I think this is related to build numbers. You'll have 1.0 build
numbers 1001, 1002,... and you vote on the specific build number.
Maven would automatically use the build number in the manifest.
On 10/16/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Ya... the build would need to use the release numbers for all those
bits, and only use the rc bits for the artifacts.
Else, you'd have to rebuild... but by rebuilding you basically
invalidate any assurance that the new build will be the same as the
rc build which presumably was voted upon. So the only real option is
to make a release build with the real release numbers internally, but
publish the jars with their rc versions. And once approved copy the
rc artifacts to the release artifacts.
--jason
On Oct 15, 2006, at 6:01 PM, Craig McClanahan wrote:
> On 10/15/06, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> just one comment: wouldn't it be better if release:accept would
>> copy the
>> 2.0.5-rcX artifacts to 2.0.5 (like in Joakim's proposal) instead
>> of doing
>> the build again ?
>
>
> Wouldn't all the internal version numbers in things like
> META-INF/MANIFEST.MF be messed up if Maven just copied and renamed the
> files?
>
> Tom
>
>
> Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
