[ http://jira.codehaus.org/browse/MRELEASE-7?page=all ]
Jason van Zyl moved MNG-1728 to MRELEASE-7:
-------------------------------------------
Version: (was: 2.0.1)
Component: (was: maven-release-plugin)
Workflow: jira (was: Maven)
Key: MRELEASE-7 (was: MNG-1728)
Project: Maven 2.x Release Plugin (was: Maven 2)
> Release versioning does not work with dependencyManagement
> ----------------------------------------------------------
>
> Key: MRELEASE-7
> URL: http://jira.codehaus.org/browse/MRELEASE-7
> Project: Maven 2.x Release Plugin
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
