On job as freelancer working with Java, JDK17+, Jenkins, Maven, Docker, K3S, Git, In my spare time I'm trying to blog about something useful(?) or try to hack on things I like.
I recommend to use the versions-maven-plugin like this:
mvn versions:display-dependency-updates
In particular related to using spring boot including the bom file you can configure the versions-maven-plugin to limit the output on the bom updates instead of the deps updates itself... mojohaus.org/versions/versions-mav...
My script will only report on version differences if a dependency has a version explicitly declared in pom files. Only the spring-boot-starter-parent would be reported:
On job as freelancer working with Java, JDK17+, Jenkins, Maven, Docker, K3S, Git, In my spare time I'm trying to blog about something useful(?) or try to hack on things I like.
I recommend to use the versions-maven-plugin like this:
In particular related to using spring boot including the bom file you can configure the versions-maven-plugin to limit the output on the bom updates instead of the deps updates itself...
mojohaus.org/versions/versions-mav...
These have slightly different behavior.
The plugin will complain about all spring-boot dependencies, even if only
spring-boot-starter-parenthave a explicit version declared:My script will only report on version differences if a dependency has a version explicitly declared in pom files. Only the spring-boot-starter-parent would be reported:
The issue is that you used the plugin based on no configuration... instead of correctly configuring it:
Based on the above configuration you can now call:
That will printout only the updates for the bom's only ... or direct dependencies:
Wow, it's a non-trivial configuration... No wonder I didn't find it in the documentation. Thanks for sharing.