[
http://jira.codehaus.org/browse/MRELEASE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186822#action_186822
]
Dave Copeland commented on MRELEASE-159:
----------------------------------------
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):
# 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)
# apply the patch
# Change the {{groupId}} and {{version}} in *all three* poms (this helps you
deploy it later)
# build everything
# deploy these files to your local maven repo
# Change your poms that reference the release plugin to reference the one you
built via the new {{groupId}} and the new {{version}}
> 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
