Jukka Zitting wrote:
Why not just change the version in the pom.xml to 1.2.0-rc1 before
doing the rcX
release? If you use the maven release plugin this means no extra work
at all.
This way files like manifest etc should contain the right version
number. If
there are files that don't take the version number of the pom.xml, we
should
consider adjust the build process.
This is exactly what we do. The problem is that we can't use the -rcN
builds for the final release vote since we don't want the -rcN suffix
to be a part of the official release packages.
Ok, I see. Shouldn't it be possible to check out the revision you used to create
the 1.2.0-rcN release and release it again as 1.2.0? I'm not quite sure how the
release plugin handles this.
Cheers,
Christoph
