So I've been mis-interpreting the way the build number would be used. My organization has separate UAT [user acceptance test] and production environments. Nothing gets to production that hasn't been through UAT.
The development group distributes artifacts to the group responsible for deployment into these environments via an internal remote maven repository. Generally, we convey the artifacts to the repo using the 'release' plugin, which I understand relies on the 'deploy' plugin. We've been forced to advance version numbers when deploying successive fixes/refinements in UAT so that the artifacts can be differentiated. I.e. we can't release 1.2.3, have it placed in UAT, and then release another 1.2.3 with very minor tweaks because it can't be [easily] distinguished from the first one. So we release 1.2.4, even though 1.2.3 was never a true production version. UAT is effectively an extension of the QA process. I was hoping that build number would let us iteratively refine an artifact in UAT without relying on version number alone. It sounds like the best that can be done is to inject the build number into jar/war manifest files. Brad > -----Original Message----- > From: Wendy Smoak [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 13, 2008 6:19 PM > To: Maven Users List > Subject: Re: buildnumber value not making it to local repo > > On Thu, Nov 13, 2008 at 5:14 PM, Harper, Brad > <[EMAIL PROTECTED]> wrote: > > I've configured the buildnumber plugin to attach a timestamp > ... > > But the build number is not carried into the local repo when > > installing the artifact. > > The finalName in the pom does not affect the filename in the > repository. > > The repository format is fixed so that Maven understands how > to retrieve artifacts. That's not to say it *couldn't* be > changed, but currently there is just the one implementation. > > And we really need to put this in the FAQ. :) > > -- > 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]
