[
http://jira.codehaus.org/browse/MRELEASE-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170773#action_170773
]
Hafga commented on MRELEASE-7:
------------------------------
The problem ist still available in Maven 2.0.10
> Release versioning does not work with dependencyManagement
> ----------------------------------------------------------
>
> Key: MRELEASE-7
> URL: http://jira.codehaus.org/browse/MRELEASE-7
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Reporter: Mike Perham
> Assignee: Brett Porter
> Attachments: scm-test.zip
>
>
> We use a top-level <dependencyManagement> block in our root POM to hold all
> versions. Children reference group/artifact but do not specify the version
> in their own POMs. When I prepare a top-level release of the parent and
> children, the child POMs have the versions added and the parent POM still
> contains the old version.
> Attached is a very simple project set. Update the SCM connection, do a
> release:prepare and examine the parent and scmwar's POM.
--
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
