Hello Robert, The analyze dependency management goal of the dependency plugin[1] can fail the build if there are any dependency management overrides. You can run that with a CI server on al of your builds and discuss the results with the teams.
[1] https://maven.apache.org/plugins/maven-dependency-plugin/analyze-dep-mgt-mojo.html Hth, Nick Stolwijk ~~~ Try to leave this world a little better than you found it and, when your turn comes to die, you can die happy in feeling that at any rate you have not wasted your time but have done your best ~~~ Lord Baden-Powell On Sat, May 4, 2013 at 8:39 AM, Mirko Friedenhagen <[email protected]>wrote: > Hello Robert, > > you could use the enforcer-plugin to enforce specific versions, then at > least you have an easy way to identify those projects. We exclude all > versions of spring and then include the latest version again, e.g. > > Regards Mirko > -- > Sent from my mobile > On May 4, 2013 12:54 AM, "Enyedi, Robert" <[email protected]> wrote: > > > Hi, > > > > We're using a parent POM which manages the versions of tens of > > dependencies. I occasionally encounter modules within my group that > > override some of those managed versions. > > > > Assuming the overrides are not legit, is there an automatic way to remove > > them from the child POMs? I was hoping that the > > versions:update-child-modules mojo would help, but it doesn't seem to do > > what I need. > > > > Thanks, > > Robert > > > > >
