gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <>
Subject Re: now, why isnt this working?
Date Thu, 28 Sep 2006 10:16:09 GMT
Stefan Bodewig wrote:
> On Fri, 22 Sep 2006, Steve Loughran <> wrote:
>> The first subsidiary build works, but the second is failing
> It gets further now, and fails in an expected manner since the test is
> supposed to fail under Gump.

I've patched the gump descriptors to set a property, one I'll use to 
switch off ant runs. That assumes that <antunit> passes command line 
properties all the way down, of course

> What I've done is that I added a <mkdir> for the <work> entry of the
> failing build.  I thought we had left this problem behind with JDK
> 1.4+ but it seems to be raising its ugly head again.
> In JDK 1.3 you needed to add <mkdir>s for each <work> that was created
> during the build, if you need classes from those directories in <java>
> or non-forked <junit>s.  The reason was that the VM would drop all
> CLASSPATH entries that didn't exist at startup time.
> What we have now seems to be a variant thereof.  I don't think it is
> related to <antunit>, but then again we haven't seen the problem with
> any other task lately.

It may be that I'm chaining <ant> and <ant> too far down

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message