On Fri, 26 Apr 2002, Christopher Lenz wrote: > Howdy folks, > > I've been playing with Maven, and it kicks major ass. > Congrats to all involved. > > Being involved in the Jakarta Slide project, I've toyed around trying > to mavenize it... however Slide does use some conventions that don't > seem to map to the project object model all too well. > > 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. > > 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 Glenn McAllister SOMA Networks, Inc.
