Hi Bruno,
You can define a property in a project all projects inherit from
<properties>
<dep.cglib.cglib>3.2.4</dep.cglib.cglib>
Then add a dependencyManagement section that sections the version
<dependencyManagement>
<dependencies>
<dependency>
<groupId>cglib</groupId>
<artifactId>cglib</artifactId>
<version>${dep.cglib.cglib}</version>
And use this plugin to check for updates etc
https://www.mojohaus.org/versions-maven-plugin/
Delany
On Thu, 2 Sept 2021 at 16:40, Bruno <x.ma...@melloni.com> wrote:
> I have been developing in Java almost from the beginning, but have not
> used Maven for much more than a few personal test apps. I am now about
> to migrate nearly 100 applications to Maven and I am a bit concerned
> about how to manage dependency versions across that many projects in the
> future.
>
> For a single app it is simple, go into the POM, modify the version of
> the dependency, then verify that nothing broke due to newly unsupported
> methods and fix the issues.
>
> But if you have a lot of applications, the above method becomes very
> time consuming and manual.
>
> QUESTION: Is there a best practice (or perhaps tools that help) for how
> to handle updating the dependency versions for that many applications?
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
