Hi Glenn, thanks for the response.
Am 26.04.2002 17:07:26, schrieb "Glenn A. McAllister" <[EMAIL PROTECTED]>: >On Fri, 26 Apr 2002, Christopher Lenz wrote: [...] >> The main problem is that Slide consists of a set of modules that are >> maintained in a single cvs-repository. There is the core module (the >> kernel), and a lot of additional modules that may or may not depend >> on the kernel. These modules also have a varying set of external >> dependancies, and in addition most of them are compiled into their >> own JAR file. > >My preferred solution to this is to allow multiple project.xml files, >specified in the delegating build.xml (defaulting to project.xml). I >haven't a clue how others feel about this. Hmm, but the modules/components do also have a lot in common, e.g. the mailing lists, the cvs repo, the developers, the documentation/site. Metric results and possibly source xreference should span all components. Also the component JARs do get bundled into web-applications at the end of the build. Maybe you're right (I'm totally new to Maven after all ;)), but I can't see how the problem could be elegantly solved by allowing multiple project.xml files. It might work, but it'd be quite a hack, no ? >> So I'm wondering... are there any plans to enhance the POM to include >> module specifications, each with a independant set of: >> - source directories >> - dependancies >> - target JAR file >> - target javadoc directory >> - (probably more) >> or does this somehow conflict with the philosophy behind Maven ? > >Again, the ability to specify a different project.xml file would solve >these issues. My $0.02CDN. -chris _______________________________________________ /=/ cmlenz at gmx.de
