ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject AW: [GUMP@brutus]: Project test-ant (in module ant) failed
Date Mon, 13 Dec 2004 10:57:40 GMT
Just think about "why three times ant.jar":

  <depend project="dist-ant" inherit="all"/> sais
  "For both script and ant based builds, any jars defined by the 
  specified project as outputs are added to the CLASSPATH prior 
  to invoking the build operation, unless you nest a <noclasspath> 
  element into the <depend> element." 
therefore all <jar>s of dist-ant are on the classpath for test-ant.
--> dist-ant: <jar name="lib/ant.jar" id="ant"/>   OK

Other choices are "all" which will copy all dependencies [...] into the list
of jars 
exported by this project.
So we have to see at dist-ant: 

  <depend project="ant" inherit="all"/>
  <jar name="lib/ant.jar" id="ant"/> -- already discussed

  <depend project="bootstrap-ant"/>
  <jar name="lib/ant.jar" id="ant"/> -- earned by inherit=all

  <jar name="lib/ant.jar"/> -- earned by standard <depend> behaviour (see

But three times the ant.jar is registered with id=ant. Why all three are
given to test-ant? Shouldnt the id be overriden?


> -----Urspr√ľngliche Nachricht-----
> Von: Stefan Bodewig []
> Gesendet am: Montag, 13. Dezember 2004 11:15
> An:
> Betreff: Re: [GUMP@brutus]: Project test-ant (in module ant) failed
> On Mon, 13 Dec 2004, Jan Materne <> wrote:
> > Hhm if I read the descriptor [1] in the right way, we have
> You do.  But the dependency on dist-ant shouldn't drag along the jars
> from "ant" and "bootstrap-ant".  Well, yes, it does, because of the
> inherit="all".
> I'll try to fix the inheritance logic inside the descriptor, it's not
> Gump's fault.
> Stefan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message