[
https://jira.codehaus.org/browse/MRELEASE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290414#comment-290414
]
Dmitry Katsubo commented on MRELEASE-293:
-----------------------------------------
Can anybody confirm that the problem can be workarounded, if one uses
<tagNameFormat>@{project.version}</tagNameFormat> in pom.xml (as stated in
[Overriding the default tag name
format|http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html#Overriding_the_default_tag_name_format])?
> Value of ${project.version} is captured before version resolution
> -----------------------------------------------------------------
>
> Key: MRELEASE-293
> URL: https://jira.codehaus.org/browse/MRELEASE-293
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-6
> Environment: OS X 10.4.9, Java 5, Maven 2.0.6
> Reporter: Jarrod Carlson
>
> Our organization uses tags in which are the product version and only the
> product version:
> /tags
> /2.0.1
> /2.0.2
> ....
> /2.1.12
> The default value of <tag> is "${project.artifactId}-${project.version}" as
> specified in MRELEASE-53.
> However, when I specify the value of <tag> as follows:
> <tag>${project.version}</tag> --or-- <tag>${version}</tag>
> release:prepare resolves this to "artifact-x.y.z-SNAPSHOT".
> In other words, when a <tag> is specified, it is taken before the release
> process finalizes the release number.
> While I can specify the release on the command line, I need to be able to
> batch mode this process.
> <tag>${project.version}</tag> should resolve to: "2.0.2" (or x.y.z).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
