[mojo-dev] [jira] (MVERSIONS-218) versions:set Updating wrong dependency in child projects

[Christian Schmid (JIRA)]

Christian Schmid created MVERSIONS-218 versions:set Updating wrong dependency in child projects Issue Type: Bug Affects Versions: 2.0 Assignee: Unassigned Attachments: Example.zip Created: 26/Apr/13 11:24 AM Description: I've got the following multi module project structure, consisting in a parent project with two modules: parent-project |-project-a |-project-b When I set the version of a dependency in the parent-project using the versions:set goal, it works as expected. But the command also sets the given version number to a totally different dependency (different groupId, different artifactId) in one of the sub projects. I use the following command on the parent project: mvn -N versions:set -DoldVersion=2.3-SNAPSHOT -DnewVersion=1.2.3 -DartifactId=example -DgroupId=org.any.group -DprocessParent=false -DprocessPlugins=false -DprocessProject=false -DupdateMatchingVersions=false I attach an example project to this issue, which shows the behaviour. Expected result after execution of the above command: No changes in any files (because org.any.group.example isn't referenced anywhere) Actual result after execution of the above command: pom of "project-b" changed: Version of dependency for 'project-A' is changed to '1.2.3' Environment: Windows, Java 7, Maven 3.0.4 Project: Maven 2.x Versions Plugin Priority: Major Reporter: Christian Schmid

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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