RE: Question on Module.xml

Well the intention is you specify in module.xml, and don't have to duplicate
in a build.xml because Centipede/Ruper (1) set classpaths (2) go and get the
"latest/best fit" version of the libraries for you need (keeping you up to
date).

Meaning -- rather than manual manage files & classpaths in ant scripts, you
manage higher level (project) metadata. The module.xml plays other roles for
other things (so is more re-usable than ant scripts) see:

    http://jakarta.apache.org/gump/module.html

That said, we are (slowly) working towards decoupling all the benefits of
centipede from each other, so you could use various aspects (the re-usable
cents/antlibs say) without others (e.g. project metadata).

regards

Adam
  -----Original Message-----
  From: [email protected]
[mailto:[email protected]]On Behalf Of NIkunj
Manocha
  Sent: Thursday, July 24, 2003 10:40 PM
  To: [email protected]
  Subject: Question on Module.xml


  HI All,

    I somehow got confused along the way. Please clarify my doubt.
    If I am importing the build.xml in my centipede file, and have specified
in the ant tasks all the classpaths to the different third party jars etc
needed by the project, then why do I still need to specify the same jar
files in the module.xml. What I am asking is that what purpose is served by
specifying the depend project in the module.xml. I can run the junit test
through the ant build file itself, so the classpath passing is adequate in
itself.
    Is it that the cents such as javasrc, junit etc also need to know about
the 3rd party jars and hence we absolutely must specify the depend project
attributes in the module.xml?
    Please clarify. Thanks,

  Regards,
  Nikunj