[
http://jira.codehaus.org/browse/MRELEASE-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249463#action_249463
]
Pedro Rodriguez commented on MRELEASE-412:
------------------------------------------
The unit tests couldnt show it because the problem occurs at the integration
level of the release phases.
The rewrite-poms-for-release phase changed the property only in the xml.
During the rewrite-poms-for-development, the new xml (with the "release"
version value) get parsed. However, the same unchanged reactor project (with
the previous development property value) is used.
The development version is not set during the rewrite-poms-for-development
phase because the value of the property in the xml is not the same that in the
project model.
Fix: The project model needs to be updated when we change a property value.
We have fixed this issue at the same time that the MRELEASE-454
> release:prepare does not update properties during
> rewrite-poms-for-development phase.
> -------------------------------------------------------------------------------------
>
> Key: MRELEASE-412
> URL: http://jira.codehaus.org/browse/MRELEASE-412
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-8
> Environment: Maven version: 2.0.10-RC8
> Java version: 1.5.0_14
> OS name: "linux" version: "2.6.28.4" arch: "i386" Family: "unix"
> Reporter: Christian Schulte
> Priority: Blocker
> Attachments: MRELEASE-412.patch
>
>
> When a dependency version is specified using a property like
> ${someExpression} that property is correctly updated during the
> rewrite-poms-for-release phase but not during the
> rewrite-poms-for-development phase. The attached patch solves this for me.
--
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
