On Jan 27, 2009, at 10:17 AM, Michael Hast wrote:
> I see. Thanks. Running it with -verbose I get:
> Cause by: You specified eclipse="true", but /Users/mhast/.../
> DSSAntTools/.classpath does not exist.
That sounds like you have included this project as a WO Library, but
it is not a WO Library.
> Make sense. DSSAntTools does not have a .classpath file. We have one
> folder (DSSAntTools) that contains the build files (build.xml). None
> of our applications nor frameworks contain a build.xml file. Our
> build process goes as follows:
> 1. Start build in DSSAntTools
> 2. Checkout all frameworks and applications into ~/Roots/SRCROOT
> 3. Build all frameworks and applications
>
> Is there a way to "read-in" the .classpath file when I try to build
> a framework or application?
What I do is to have a build.xml in each project that simply
references the common build file(s):
<project name="FooApp" default="build" basedir=".">
<import file="../Ant/common.xml"/>
</project>
Three lines is longer than none, but it makes building very easy.
Chuck
>
>
> Michael.
>
> Mike Schrag wrote:
>>> generic.xml:52 (line of wocompile)
>>> Failed to process eclipse frameworks.
>> ant is worthless .. run with -verbose to have any chance at knowing
>> why it failed.
>> ms
>
> --
> Tel: (520) 572-9410
> Desert Sky Software: www.desertsky.com
> Specializing in the Development and Hosting of
> e-Business Applications.
>
-- 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 : Tue Jan 27 2009 - 18:16:25 EST