I do not see such a change as a good idea. If you want to have the versions updated, just add a version tag to deps...
If you want to experiment use help:effective-Pom to generate a temp Pom and run versions on that Pom (which will have versions tags on all deps) On Wednesday, 23 May 2012, Achim Abeling wrote: > Hi Stephen, > > it is allowed to manually override the version in a child project. > This does not defeat the point of depMgmt, in my opinion. So why should > the versions-maven-plugin should be able to do it, too? > > We have a parent pom with "official" versions but want to build child > projects with "unofficial" versions. This is where we want to override > the version in the child pom. > > I am searching for a solution for a build pipeline where a project A is > build using the latest version of project B. Perhaps I can achieve what > I want by using some kind of "unofficial" parent pom whose versions are > updated as you suggested. I will see. > > I tried to patch your plugin such that it is able to add a version > element to the pom. Perhaps you'll want to use it if you change your mind. > > Thanks for your answers. > > Best regards > Achim > > > On 22.05.2012 16:28, Stephen Connolly wrote: > > The guiding principal is that only explicit versions are modified. If > > it introduced an override into project A then that would defeat the > > point of depMgmt in P. > > > > If you run the plugin on project P's pom, it will process the deps and > > the depMgmt by default, i.e. see > > > > > http://mojo.codehaus.org/versions-maven-plugin/use-latest-versions-mojo.html#processDependencyManagement > > > > -Stephen > > > > On 22 May 2012 14:32, Achim Abeling > > <achim.abel...@freenet-ag.de<javascript:;>> > wrote: > >> Is there a reason why the plugin cannot update versions from managed > >> dependencies? > >> > >> If I have to define a version in my project A for dependency B the > >> dependencyManagement in my parent pom gets rather useless, isn't it? > >> > >> Best regards > >> Achim > >> > >> On 22.05.2012 13:54, Stephen Connolly wrote: > >>> 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<javascript:;>> > 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 > >>> > >>> > >> > >> --------------------------------------------------------------------- > >> 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 > > > > >
