I remember that someone successfully built JBoss using Maven. I can't remember who it was, or where was that documented.
I'm not a Maven fan, but with jars not being part of the repository anymore, we could host different sub-projects in a hierarchical way:
/cvsroot/jboss/projects/ /cvsroot/jboss/projects/jms /cvsroot/jboss/projects/nukes /cvsroot/jboss/projects/jboss /cvsroot/jboss/projects/jboss/common ... /cvsroot/jboss/projects/jboss/varia
Each directory with it's own maven.xml
I'm not a Maven wiz, maybe somebody who is could suggest a better layout.
But if thidparty jars dependancy and innecessary jar downloads are our problems, then Maven is the solution, IMHO. We could solve 2 problems then: thirdparty hacks and build.xml redundancy. In the end, we could have ONE cvs module, "like every one else" hehe :-)
Ricardo Arg�ello
Scott M Stark wrote:
The problem is that we do alternate release builds off the different slices of the cvs modules, nukes, jmx, jmx-remoting, jms, etc. I'm all for cleaning up the build, but there really is not one monolithic release. What is your suggestion for a reorg that allows for obtaining a jmx build that does not have to pulling in tens of uneeded MBs of code and thirdparty jars?
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
