----- Original Message -----
From: "Sam Ruby" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, August 18, 2001 1:02 PM
Subject: Re: cvs commit: jakarta-alexandria/proposal/gump/project
jakarta-commons.xml
> Vincent Massol wrote:
> >
> > Here is my understanding. Before the 18th, Ant was not applying the
> > "build.sysclasspath=only" for taskdef-defined tasks, so it was working
> fine.
> > They have changed so that now it does, thus the classpath defined in a
> > taskdef is ignored ? And thus, we need to externally generate the Cactus
> ant
> > jar before ....
> >
> > Is that correct ?
> > It's getting complex ... and thus fragile .... :-)
>
> It is my understanding that build.sysclasspath=only has always applied to
> taskdefs. The way I got around this in the past was to add your work
> directories to the classpath.
oh ok, I remember now ... so you're saying that the fact GUMP reported a
failed build this morning was a pure coincidence and that nothing was
changed ? What you're also saying is that you're no longer adding the work
directory as part of the initial classpath but rather building the cactus
ant jar beforehand and adding this jar to the classpath ?
>
> The root problem as I see it is the dependency on the "clean" target by
the
> "dist" target. This causes the work directories AND the cactus-ant.jar to
> be rebuilt. This has been known to confuse class loaders and even trap
> certain JVMs.
>
> You might want to consider removing this dependency.
hum ... why not ... but .... I used the dist target to build a full
distribution and I wanted to make sure that there no previous leftover from
other targets. What do you suggest ?
Thanks
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
