Hi Marc,
make sure the ant.* files are in the cvs. WOLips generates them
whenever you change the classpath in Eclipse.
<frameworks root="${wo.wolocalroot}">
<patternset>
<includesfile name="ant.frameworks.wo.wolocalroot"/>
</patternset>
</frameworks>
with the ant.frameworks.wo.wolocalroot file
foo.framework
is the same as
<frameworks root="${wo.wolocalroot}">
<include name="**/foo.framework"/>
</frameworks>
If you see a ant.* file with content like "An empty file result in a
full filesystem scan" means that your Eclipse project has zero
references to frameworks under this root.
Ulrich
>
On Tuesday, 23. September 2003, at 22:52PM, Marc Respass wrote:
> Hi,
>
> Using woproject_1.0.7.23, I am trying to write a build script to build
> my applications. Eventually, the script will run on Solaris and it
> will checkout from CVS, build, deploy, then clean up. So far, things
> are very good but my application's classpath is not complete and I
> don't know how to fix it.
>
> I used this for woapplication
>
> <woapplication name="${project.name}" stdFrameworks="true" chmod="+x"
> destDir="${dest.dir}"
> principalClass="com.amsweb.AMMOService.Application">
>
> then copied the framework information from the WOLips build.xml so I
> have an entry like below for each library directory.
>
> <frameworks root="${wo.wolocalroot}">
> <patternset>
> <includesfile name="ant.frameworks.wo.wolocalroot"/>
> </patternset>
> </frameworks>
>
> Maybe that is the problem? The example files are very small and did
> not use the same things that the WOLips build.xml file does.
>
> Anyone have any ideas? I'm really close to having a nice build script.
> No more will the admins hassle me because I didn't give them explicit
> instructions! :)
>
> Thanks
> Marc
>
This archive was generated by hypermail 2.0.0 : Wed Sep 24 2003 - 04:49:22 EDT