maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergio Fernandes (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRELEASE-150) Can't add prefix to tags without affecting version
Date Fri, 28 Nov 2008 13:02:19 GMT

    [ http://jira.codehaus.org/browse/MRELEASE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155735#action_155735
] 

Sergio Fernandes commented on MRELEASE-150:
-------------------------------------------

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

Adding these variables seems to be very easy and valuable.

> 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
>    Affects Versions: 2.0-beta-4
>            Reporter: Yuri Schimke
>            Priority: Minor
>
> 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

        

Mime
View raw message