You could, I guess.. Really though, what makes the two projects different? How is version 1 versus version 2 different if they have the same source etc? Is it that they are two versions of the same codebase, ergo two sets of tags in Source Control... Or, is it one codebase that is cut up and output as two separate artifacts. Again, in that case, you should make it two projects.
The second project.xml file might work, but when you start doing cool/whacky tricks like that, you should go back to Ant.. Something at somepoint in Maven land will get you when you try and do two project.xml's.. Eric -----Original Message----- From: Rick Mann [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 12, 2005 5:36 PM To: Maven Users List Subject: Re: Maven help for building 2 versions for a component build On Jan 12, 2005, at 14:08, Eric Pugh wrote: > It seems to me like you should have two versions tagged in CVS... > Check > out the version youw ant and build it.. Maven really encourages that > you can only build one artifact per project... One jar, one war, > etc.... Would it make sense to have a second project.xml file, that refers to the same sources as the first? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
