[
https://jira.codehaus.org/browse/MRELEASE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=273811#comment-273811
]
Aristedes Maniatis commented on MRELEASE-695:
---------------------------------------------
I can confirm. And I just wasted the last 3 hours of my life on this very
simple bug. This makes the release plugin 2.2 very broken and almost useless
for any regular user, since the tag created when you don't override
tagNameFormat is incorrect. If you are re-using the same snapshot version (eg.
2.0b1 -> 2.0-SNAPSHOT -> 2.0b2 -> 2.0-SNAPSHOT) then everything breaks when the
release cannot create the incorrect tag.
Downgrading to 2.1 solves the problem.
> 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
> 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:
> <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>
> but I got the tag 1.0-ALPHA-2-SNAPSHOT in place of 1.0-ALPHA-2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
