[mojo-dev] [jira] (MVERSIONS-115) Missing version update inside dependency

[Sergei Ivanov (JIRA)]

Title: Message Title

Sergei Ivanov commented on an issue   Re: Missing version update inside dependency @Marcus Looking at the attached example, I believe that the plugin works absolutely correctly. The dependency is declared with a specific version, which just so happened to be initially the same as parent version, but is not in any way implied from the parent version. When you are running the plugin on the command line, you are restricting the set of artifacts to be upgraded to the parent only, and this is exactly what happens: the parent version inside projectwithdependency is updated. You have got two options: Option 1. If you want dependencysimple to follow the parent version, use a ${project.parent.version} property in dependency declaration for dependencysimple. Option 2. If you want to inherit a managed version of dependencysimple from the parent, add a dependencyManagement section to the parent project, declare a dependencysimple dependency with the desired version there, and drop the version from the dependency declaration inside projectwithdependency. Add Comment   Mojo's Versions Maven Plugin / MVERSIONS-115 Missing version update inside dependency The scenario is: 1.) Parent project which defines a version 2.) Child project that does not define an explicit version (version is inherited from the parent) 3.) Another project that holds a reference to the child project mentioned before in the dependency section. Inside that dependency we have to specify the version of the project that is reference... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email