If you don't specify the version in the pom you are running on, then it will not add the version.
If you run against the P pom then it will update that one On 22 May 2012 11:36, Achim Abeling <achim.abel...@freenet-ag.de> wrote: > Hi, > > we have the following scenario: > > - project A has project P with version 1 as parent. > - project P in version 1 defines project B with version 1 in it's > dependencyManagement section. > - project A has project B as dependency without defining the version and > therefore inherits the version from the parent project P > > Normally, project A uses version 1 of project B. > > Now, there are newer versions of project B in the repository, say version 2. > > Using > # mvn versions:display-dependency-updates > on project A correctly says something like > > [INFO] The following dependencies in Dependency Management have newer > versions: > ... > [INFO] project B ..................... 1 -> 2 > > But calling > # mvn versions:use-latest-versions > does not change the pom.xml. > > I would expect the versions-plugin to add > <version>2</version> > to the dependency definition for project B. > > What can I do? > > > Thanks > Achim > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
