[jira] Commented: (MRELEASE-293) Value of ${project.version} is captured before version resolution

2009-09-14 Thread Dmitry Katsubo (JIRA)

[ 
http://jira.codehaus.org/browse/MRELEASE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=190879#action_190879
 ] 

Dmitry Katsubo commented on MRELEASE-293:
-

Currently I see only one workaround for the issue:

1. Specify {{project.rel.org.codehaus.mojo}} and/or 
{{project.dev.org.codehaus.mojo}} from the commend line (see here 
http://maven.apache.org/plugins/maven-release-plugin/examples/non-interactive-release.html
 for more details):

-Dproject.rel.org.codehaus.mojo:jaxws-maven-plugin=1.12.1 
-Dproject.dev.org.codehaus.mojo:jaxws-maven-plugin=1.13-SNAPSHOT

2. Refer then this information from {{pom.xml}}:

  build
plugins
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
configuration
  
tagBasehttps://myserver.com/svn/public/tags/java/jaxws-maven-plugin//tagBase
  tag${project.rel.org.codehaus.mojo:jaxws-maven-plugin}/tag
/configuration
  /plugin
/plugins
  /build


 Value of ${project.version} is captured before version resolution
 -

 Key: MRELEASE-293
 URL: http://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 contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MRELEASE-293) Value of ${project.version} is captured before version resolution

2008-10-24 Thread Luc Willems (JIRA)

[ 
http://jira.codehaus.org/browse/MRELEASE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=151823#action_151823
 ] 

Luc Willems commented on MRELEASE-293:
--

same problem here.

useing tag${version}/tag resolves into snapshot versions in the final TAG 
name.

maybe we should change tag info prefix-tag and append runtime version during 
release proces.


 Value of ${project.version} is captured before version resolution
 -

 Key: MRELEASE-293
 URL: http://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 contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira