You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jeff Skjonsby (JIRA)" <ji...@codehaus.org> on 2010/07/15 20:29:32 UTC
[jira] Updated: (MRELEASE-150) Can't add prefix to tags without
affecting version
[ http://jira.codehaus.org/browse/MRELEASE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Skjonsby updated MRELEASE-150:
-----------------------------------
Attachment: release-manager-patch.patch
Here's a patch with unit tests that adds simple substitution for [groupId], [artifactId], and [version] in the release label.
> Can't add prefix to tags without affecting version
> --------------------------------------------------
>
> Key: MRELEASE-150
> URL: http://jira.codehaus.org/browse/MRELEASE-150
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.0-beta-4
> Reporter: Yuri Schimke
> Priority: Minor
> Attachments: release-manager-patch.patch
>
>
> I added the following to my POM
> <plugin>
> <artifactId>maven-release-plugin</artifactId>
> <configuration>
> <tag>XXX-${artifactId}-${version}</tag>
> </configuration>
> </plugin>
> However the tag comes out incorrectly.
> [INFO] Full run would be tagging C:\PerforceViews\... with label: 'XXX-myproject-0.5.4-SNAPSHOT
> What is the default? <tag>${artifactId}-${version}</tag>
> Note: this seems to be missing from the plugin documentation, it only mentions releaseLabel, which defaults to tag.
--
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