On Tue, 2004-03-02 at 19:52, Brian Enigma wrote: > I am in the process of evaluating Maven to replace or coexist with > our existing Ant build process. For final release projects, Maven is > great because I can tell it where to find mycompany-crypto.jar, etc. > For this core "util" project, I am having difficulty figuring out how > to best model the behavior I need in Maven. Is there a way to have a > single project.xml output half a dozen jar files--one for each package?
This is something that is discouraged in Maven which is why there is only one allowable entry for the source directory. If you have multiple jars being output where each JAR addresses a different concern then what Maven encourages is that you put these in separate projects. > > Will I have to resort to multiple project files (project-crypto.xml, > project-xml.xml, etc) with one master project.xml to bind them all? We don't consider this a "last resort", we consider this normal. > Should I stick with the existing Ant scripts in this one case? No, I would suggest you break up your build. But if you want to output many JARs from one build then stick with Ant. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
