You could start a release branch with the release plugin and start releasing release candidates, like 1.2.3-RC1, 1.2.3-RC2, etc, until you have a final release and release that as 1.2.3.
Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Fri, Nov 14, 2008 at 1:44 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > 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/apache/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]
