RE: Question on Module.xml

Hi Adam,
 
Thanks for the explanation. Now I ubderstand.
 
Vlad

-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of Adam Jack
Sent: Friday, July 25, 2003 3:24 PM
To: [email protected]
Subject: RE: Question on Module.xml


Yeah,  I think the dots there are confusing it. What is a name, what is a version, what is an extension? Kinda hard of a parser. Luckily the more traditional format is:  log4j-1.2.6.jar (name dash version [dash sub-type] dot extension. For more details see http://www.krysalis.org/ruper, which was based off a number of conventions from Jakarta to others.
 
With that, and as such you ought be able to "ask" (in module.xml) for "log4j", i.e. <depend name="log4j" /> and have it get log4j-{version}.jar for you.
 
If you registered this repository at ibiblio.org ( http://www.ibiblio.org/maven/%name%/) then Ruper would automatically get you the jar for log4j from here http://www.ibiblio.org/maven/log4j/jars/. The entry in your module.xml would be:
 
    <jars repository="maven"  url="http://www.ibiblio.org/maven/"/>
 
Alternatively (and what I recommend) is you manage your own repository via an intranet URL to a local server (or file) so you can update it yourself and have all your builds get the right jar.
 
regards
 
Adam

-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of Nevzorov, Vlad
Sent: Friday, July 25, 2003 7:48 AM
To: [email protected]
Subject: RE: Question on Module.xml


Adam,
 
To let you know - I have found a problem while adding jars to module.xml. It doesn't find jars with dots (".") in the names. For example, it can't find log4j.1.2.6.jar but finds log4j_1_2_6.jar alright. It's not a problem, but uncinvenience.
 
Thanks,
Vlad

-----Original Message-----
From: Adam Jack [mailto:[email protected]]
Sent: Friday, July 25, 2003 2:39 PM
To: [email protected]
Subject: 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>     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