> Do you require the full release process with a tag for every > one of these versions, or would unique snapshots (with the > revision number baked inside) work for you?
We don't *require* tags at each iteration, but since its been our practice to use the 'release' plugin to deploy, extra tags are a by-product. The tagged release that makes it into production is required. > This is a good idea regardless. :) Agreed. Brad > -----Original Message----- > From: Wendy Smoak [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 13, 2008 6:44 PM > To: Maven Users List > Subject: Re: buildnumber value not making it to local repo > > On Thu, Nov 13, 2008 at 5:33 PM, Harper, Brad > <[EMAIL PROTECTED]> wrote: > > > I was hoping that build number would let us iteratively refine an > > artifact in UAT without relying on version number alone. > > Do you require the full release process with a tag for every > one of these versions, or would unique snapshots (with the > revision number baked inside) work for you? > > Here's an example of the version numbers: > http://people.apache.org/repo/m2-snapshot-repository/org/apach > e/tiles/tiles-core/2.0.7-SNAPSHOT/ > > > It sounds like the best that can be done is to inject the > build number > > into jar/war manifest files. > > This is a good idea regardless. :) > > -- > Wendy > > --------------------------------------------------------------------- > 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]
