If that's the case then maybe take a look at the analyze-dep-mgt goal of the dependency plugin.[1]
Hth, Nick Stolwijk [1] https://maven.apache.org/plugins/maven-dependency-plugin/analyze-dep-mgt-mojo.html ~~~ 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 Tue, Jan 29, 2019 at 11:42 AM Mikael Åsberg <m.asberg.wa...@gmail.com> wrote: > He wants to ensure that no managed versions I are overridden. > > On Jan 29, 2019 11:40, "Tamás Cservenák" <ta...@cservenak.net> wrote: > > So, if I understand correctly: to enforce there is no reactor project in > depMgt section of child modules? > > On Tue, Jan 29, 2019 at 12:48 AM Jörg Schaible <joerg.schai...@gmx.de> > wrote: > > > > On Mon, 28 Jan 2019 22:34:56 +0100 Harald Wellmann wrote: > > > > > Do you mean a rule to enforce no snapshot dependencies? In that case, > > > there is a rule called "requireReleaseDeps". > > > > No. > > > > > "No local versions" does not really make sense to me, because any > remote > > > dependency will first be downloaded to your local repository. > > > > It has nothing to do with repositories. We manage versions in a depMgmt > > section the parent of a multi- > > project and no-one should declare own versions for his dependencies in > the > > sub projects. > > > > Regards, > > Jörg > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > >
