[
http://jira.codehaus.org/browse/MRELEASE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186830#action_186830
]
Michael Wenig commented on MRELEASE-159:
----------------------------------------
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
> 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
> Attachments: MRELEASE-159-PATCH-update.diff.gz,
> MRELEASE-159-PATCH.diff.gz
>
>
> 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
