Mantas, why dont you use properties for versions? I found that some plugins
don't pick up artifact versions from dependencyManagement, breaking the
uniformity that depmng supposedly offers. Properties ensure a single source
of truth.
Delany
On Thu, 2 Sept 2021 at 17:35, Mantas Gridinas wrote:
>
Another way of doing this is with automation. There are various tools that
update a dependency, run the build and create a PR (or automerge).
If you are using Github, you can take a look at dependabot, but if you use
standalone tools (like bitbucket and Jenkins) you can look at renovate.
With
You might be interested in running the POM per application rather than
some global singular POM, since you should retain the ability to
update a single application's dependencies without breaking other
applications' behavior. I agree that this approach is the more time
consuming than having some
Another option is creating an artifact of type ‘pom’ that consists of just a
pom.xml with a section and optionally properties for the
versions (so they can easily be overridden when needed), and importing this BOM
(bill of materials) artifact in your applications.
See spring-boot-dependencies
Hi Bruno,
You can define a property in a project all projects inherit from
3.2.4
Then add a dependencyManagement section that sections the version
cglib
cglib
${dep.cglib.cglib}
And use this plugin to check for updates etc
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.
