Actually clarified that the release plugin is being used but the tag is being forced to a different name and then moved post successful release, e.g.
mvn release:prepate release:perform -DreleaseVersion=3.1.0 -Dtag=3.1.0-RC1 Now there is an issue with that in that the pom will contain the wrong tag in the scm section... $ svn log --limit 5 -v https://svn.apache.org/repos/asf/commons/proper/compress/tags/COMPRESS-1.5 ------------------------------------------------------------------------ r1456364 | bodewig | 2013-03-14 08:43:27 +0000 (Thu, 14 Mar 2013) | 1 line Changed paths: A /commons/proper/compress/tags/COMPRESS-1.5 (from /commons/proper/compress/tags/COMPRESS-1.5_RC1:1456363) Vote has passed, 1.5 is released ------------------------------------------------------------------------ r1455005 | bodewig | 2013-03-11 06:10:51 +0000 (Mon, 11 Mar 2013) | 1 line Changed paths: A /commons/proper/compress/tags/COMPRESS-1.5_RC1 (from /commons/proper/compress/trunk:1455004) M /commons/proper/compress/tags/COMPRESS-1.5_RC1/pom.xml Tagging first RC for Compress 1.5 ------------------------------------------------------------------------ So they are not using the release plugin then... perhaps a pseudo-tag option is needed for the release plugin then... On 29 May 2013 13:40, Barrie Treloar <[email protected]> wrote: > On 29 May 2013 20:53, Stephen Connolly <[email protected]> > wrote: > > The issue with that is when using the Maven Release Plugin, you will not > be > ... > > Can't we fix the tooling then? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
