Benson Margulies created MVERSIONS-184:
------------------------------------------
Summary: complex parent-child relationships stop decent into
children
Key: MVERSIONS-184
URL: https://jira.codehaus.org/browse/MVERSIONS-184
Project: Maven 2.x Versions Plugin
Issue Type: Bug
Affects Versions: 1.3.1
Reporter: Benson Margulies
I created a project with packaging=pom and a series of modules. The modules'
parent elements do NOT point to the new project. One of the modules in the list
is the common parent of the other. All of the poms agree as to their current
version number.
mvn versions:set -DnewVersion=FOO
Further, these poms get their <version> from their parent; the parent has a
version, and the pom does not override it. Since processParent is supposed to
be true by default, I'd expect this to work.
only changes my new POM, not the other poms. -X suggests that the plugin has
decided to stick with the existing version.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
