I'm sorry. I wasn't referring to using "mvn versions:display-dependency-updates" as a bad practice. That tool is really helpful. What I meant to identify as not being a good practice is to use dependency ranges [,).
On Apr 6, 2017 12:03 PM, "Bill Mair" <[email protected]> wrote: I pointed to "display-dependency-updates", it ONLY lists the available updates and you have to edit the pom yourself. Why is that bad practice? On 06/04/17 21:01, Elliot Huntington wrote: This is not a good practice to follow if you want reproducible builds. It is better to manage your dependencies manually. On Apr 6, 2017 11:56 AM, "Bill Mair" <[email protected]> <[email protected]> wrote: See: http://www.mojohaus.org/versions-maven-plugin/ In particular "mvn versions:display-dependency-updates<http://www.mojohaus.org/versions-maven-plugin/ examples/display-dependency-updates.html> <http://www.mojohaus.org/versions-maven-plugin/examples/display-dependency-updates.html>" - The display-dependency-updates goal will check all the dependencies used in your project and display a list of those dependencies with newer versions available. -- [image: BMS Logo] *Bill Mair* Director Email : [email protected] Tel. (UK): +44(0)-7427-802931 <+44%207427%20802931> Tel. (DE): +49(0)-157-85693835 <+49%201578%205693835> www.billmairsolutions.ltd.uk Bill Mair Solutions Limited, Registered in England, Company No. 08556864 Registered office: 183 Walsall Road, Great Wyrley, Walsall, WS6 6NL
