[
http://jira.codehaus.org/browse/MRELEASE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266438#action_266438
]
Laksiri Dasun commented on MRELEASE-159:
----------------------------------------
Thanks a lot Dave. I managed to get it done. and i do a small change as well
{noformat}
+ * 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;
{noformat}
expression="${remoteTagging}" should be changed as
expression="${tagNameFormat}"
Great work Dave wonder why still it didn't released.
> Support a pattern to generate the release tag
> ---------------------------------------------
>
> Key: MRELEASE-159
> URL: http://jira.codehaus.org/browse/MRELEASE-159
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Components: prepare
> Affects Versions: 2.0-beta-4
> Reporter: Joerg Schaible
> Fix For: 2.2
>
> Attachments: MRELEASE-159-PATCH-2-0.patch,
> MRELEASE-159-PATCH-update.diff.gz, MRELEASE-159-PATCH.diff.gz,
> release-manager(updated).patch, release-manager-patch.patch
>
>
> The release-plugin uses currently the pattern "<artifactId>-<version>" to
> create the version tag. A configuration element would be fine to support
> different requirements for release tags (in our case "v_<version>", since
> with svn the module is already part of the path).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
