On Sep 8, 2008, at 10:36 AM, Mike Schrag wrote:
>> The WOPath ant task in the new Nightly wolips doesn't seem to do
>> the right thing with nested <framework> elements.
>>
>> My WOCompile task is finding the frameworks, but I need WOPath in
>> order to build the correct classpath for my autiomated unit tests…
>>
>> Am I correct (if so I'll report in JIRA) or am I doing something
>> wrong?
>>
> Let's go to step one -- wtf is WOPath :)
Some old hotness that made it easier to write reusable build files.
> I've never actually used that task, so I'm not sure what it
> does ... Can you give me an example usage + what it used to do +
> what it does now?
/**
* A subclass of Path with support for frameworks.
*
*..uthor Chuck Hill
*/
<!-- Non-source Classpath for project-->
<wopath id="project.classpath">
<frameworks dir="${user.frameworks.path}"
bundles="${app.frameworks}/${gvc.frameworks}/$
{wonder.frameworks}" />
<frameworks dir="${local.frameworks.path}"
bundles="${library.frameworks}" />
<frameworks dir="${system.frameworks.path}"
bundles="${system.frameworks}" />
<path refid="webobjects.extensions"/>
</wopath>
This is the only interesting method:
/**
* Adds a nested <code><framework></code> element.
*..aram framework FrameworkSet to add as a FileSet
*..hrows BuildException
*/
public void addFrameworks(FrameworkSet framework) throws
BuildException {
addFileset(framework);
}
Does that help any?
Chuck
-- Chuck Hill Senior Consultant / VP DevelopmentPractical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects
This archive was generated by hypermail 2.0.0 : Mon Sep 08 2008 - 13:44:12 EDT