You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Duncan Jones (JIRA)" <ji...@codehaus.org> on 2013/04/19 12:25:52 UTC

[jira] (MRELEASE-695) tagNameFormat with @{project.version} tags the SNAPSHOT version

    [ https://jira.codehaus.org/browse/MRELEASE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323945#comment-323945 ] 

Duncan Jones commented on MRELEASE-695:
---------------------------------------

I realise this is yet more circumstantial evidence, but... I just had the issue occur using v2.1 as well. So clearly this is not a valid work-around.
                
> tagNameFormat with @{project.version} tags the SNAPSHOT version
> ---------------------------------------------------------------
>
>                 Key: MRELEASE-695
>                 URL: https://jira.codehaus.org/browse/MRELEASE-695
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.2
>            Reporter: Fabrizio Giudici
>
> The much awaited (by me) MRELEASE-159 seems not to work. I tried a release with the following pom:
> {code:xml}
>             <plugin>
>                 <groupId>org.apache.maven.plugins</groupId>
>                 <artifactId>maven-release-plugin</artifactId>
>                 <configuration>
>                     <localCheckout>true</localCheckout>
>                     <preparationGoals>clean install verify</preparationGoals>
>                     <goals>clean install javadoc:javadoc assembly:assembly deploy</goals>
>                     <arguments>-P${release.profiles} -DaltDeploymentRepository="${altDeploymentRepository}"</arguments>
>                     <tagNameFormat>@{project.version}</tagNameFormat>
>                 </configuration>
>             </plugin>
> {code}
> but I got the tag {{1.0-ALPHA-2-SNAPSHOT}} in place of {{1.0-ALPHA-2}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira