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

Paul Gier commented on MRELEASE-389:
------------------------------------

{quote}
However, looking at the source, I do not understand where the command-line 
properties are pushed towards a ReleaseDescriptor object besides the method 
ReleaseUtils.copyPropertiesToReleaseDescriptor(Properties).
{quote}

Ringo,
You should be able to set the version plugin parameters through the command 
line using those properties (releaseVersion and developmentVersion).  The 
plugin parameters are configured to pick up the command line properties like 
this.

{code}
/** 
 * @parameter expression="${releaseVersion}"
 */
private String releaseVersion;
{code}

The copy properties part is only used to pick up properties that can't be set 
through the plugin parameters.  For example the module specific versions in a 
multi module release.

But if it's not working for you with 2.0-beta-8 or the beta-9 snapshot then 
there must be something else going wrong.  And if you can help me track it 
down, I can try to fix it.


> Properties releaseVersion and developmentVersion are not read correctly 
> during release:prepare (eventually release:perform)
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-389
>                 URL: http://jira.codehaus.org/browse/MRELEASE-389
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-8
>         Environment: Maven version: 2.0.9
> Java version: 1.6.0_07
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> scm=CVS
>            Reporter: jcrouvi
>             Fix For: 2.0-beta-9
>
>         Attachments: jcrouvi_20081204_test.log, Patch-MRELEASE-389.txt
>
>
> Calling
>  mvn --batch-mode release:prepare release:perform -Dtag=TEST_RELEASE-3_0_0 
> -DreleaseVersion=3.0.0 -DdevelopmentVersion=3.0.1-SNAPSHOT
> doesn't produce the expected results:
> * -DdevelopmentVersion=3.0.1-SNAPSHOT
> ** the value is not set correctly in the file pom.xml:
> *** Expected:  <version>3.0.1-SNAPSHOT</version>
> *** But was: <version>2.0.5-SNAPSHOT</version>
> * -DreleaseVersion=3.0.0
> ** the artifacts are not created correctly:
> *** Expected artifact: ipi-multimodule-b-3.0.0.jar
> *** But was: ipi-multimodule-b-2.0.4.jar
> ** the value is not set correctly in the file pom.xml (comment in CVS: 
> [maven-release-plugin] prepare release TEST_RELEASE-3_0_0):
> *** Expected:  <version>3.0.0</version>
> *** But was: <version>2.0.4</version>
> * -Dtag=TEST_RELEASE-3_0_0
> ** the value is set correctly in the file pom.xml 
> ** the tagging of the CVS module is also correct.

-- 
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

        

Reply via email to