I guess I was thinking more about a goal that took a tag, checked out the source and built. A sort of dynamic module.
On 10/18/05, Mark Kuzmycz <[EMAIL PROTECTED]> wrote: > > All you would need to do is version the pom.xml in source control. There > is no need to create a different pom.xml for each version. Just follow > your usual process: make changes and label the release (including the > pom). Reproducing a release for a previous version should be straight > forward. > > I don't think there is a need to support versioned poms within maven. > > Regards, > Mark. > > -----Original Message----- > From: Xavier Toth [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 18, 2005 9:00 AM > To: Maven Users List > Subject: [m2]versioning > > To have repeatable builds I want to be able to build specific scm tagged > versions and have dependency lists that match the given version. This > seems like it would be a very common use case, how are others solving > this problem with m2? Can you have multiple dependency lists? I don't > think so. A different pom.xml per version? That doesn't sound very good. > > > _______________ > Siebel > IT'S ALL ABOUT THE CUSTOMER > Visit www.siebel.com <http://www.siebel.com> > > This e-mail message is for the sole use of the intended recipient(s) and > contains confidential and/or privileged information belonging to Siebel > Systems, Inc. or its customers or partners. Any unauthorized review, use, > copying, disclosure or distribution of this message is strictly prohibited. > If you are not an intended recipient of this message, please contact the > sender by reply e-mail and destroy all soft and hard copies of the message > and any attachments. Thank you for your cooperation. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
