Support a pattern to generate the release tag

I have the same problem: I need to add a suffix to make the release tag match our naming pattern.

Adding variables as suggested in http://jira.codehaus.org/browse/MRELEASE-150 seems to be very easy and valuable.

We have a pattern of RLS_<artifactId>_<version> where everything is uppercase. I would be very happy if you could add support for changing case also.

Here is a patch that provides this feature. I, too, need it, as the default is redundant for our environment.

This adds the configuration option tagNameFormat that takes a Java MessageFormat string, where

-

; what it is currently).

Tests should be included to cover this. I really need this feature, so committers feel free to contact me for any changes you'd like to see.

Apologies; the previous patch is not sufficient; I underestimated the breadth of the configuration. This patch should work.

It would be good to reuse the format pattern syntax used by maven-eclipse-plugin and m2eclipse:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html#projectNameTemplate

is it possible to integrate this patch in the version 2.0-beta-10 and release it?

It's a bit urgent at my current customer...

Thanks Michael

Michael - if you are desperate and don't want to wait, you can use it now with a bit of elbow grease (this is what we're doing where I work):

1. checkout the 2.0-beta-9 via https://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.0-beta-9 (you need both the release manager and the release plugin, which this url will get you)
2. apply the patch (the latest of the two; I don't have perms to delete the bad one)
3. Change the groupId and version in all three poms (this helps you deploy it later)
4. build everything
5. deploy these files to your local maven repo
6. Change your poms that reference the release plugin to reference the one you built via the new groupId and the new version

Hi Dave,

thanks for this workaround - that's exactly the one I have to make but leads to some discussions If there would be a new beta in the next weeks we could avoid that...

And as the patch is still there and working I think it should be possible with only little effort to apply it officially

Regards Michael

I've added another patch with unit tests that adds substitution for [groupId], [artifactId] and [version]

Example:
<tag>releases/[version]</tag>

Would it be possible to add support for making the tag uppercase?

Here's an updated patch that fixes a couple issues in the first patch. This patch has been working well in our internal release process.

I added a new patch file which is the second one from Dave ported to the final Release-Plugin Version 2.0

Note:
The patch was made against a copy of the release-tag in our local svn - so ignore the revision number

Please, please include it for the next release!

updated patch to review

Hi Dave , could you please tell me what should i write in tagNameformat inorder to get only the releseVersion as the tag.

eg: "1.0.0"

From my comment above:

This adds the configuration option tagNameFormat that takes a Java MessageFormat string, where {0} is the artifact name and {1} is the version (as such, the default is {0}-{1}; what it is currently).

So, if you just wanted the version, you can do

<tagNameFormat>{1}</tagNameForamt>

Thanks a lot Dave. I managed to get it done. and i do a small change as well

  
+     * Specify the format of the tag as a java MessageFormat string.  
+     * {0} is the artifact id, {1} is the tag version.
+     * @parameter expression="${remoteTagging}" default-value="{0}-{1}"
+     */    
+    private String tagNameFormat;

expression="$

" should be changed as expression="$

"

Great work Dave wonder why still it didn't released.

r1139359