When the target is run again, only official releases are listed to be updated.Now add the ruleset to the configuration of the plugin where /config/maven-versions-plugin-rules.xml is the relative path in your workspace where the ruleset is located:įile:///$/config/maven-versions-plugin-rules.xml.An example of a ruleset which excludes the alpha, beta, release and milestone release is listed here: It is possible to exclude these releases from the suggested updates by means of a ruleset. Taking a closer look to the complete output, we notice that also alpha, beta, release candidates, milestone releases are listed.The following dependencies in Dependency Management have newer versions: Secondly, a list is shown of the dependencies where updates are available for:.artifact :jackson-databind: checking for updates from central artifact :jackson-core: checking for updates from

artifact :jackson-databind: checking for updates from First, a list is shown of the dependencies which are checked.Run the target which gives us an overview of the dependencies which need to be updated:.But we will notice that this is not sufficient in order to have the wanted behavior of the plugin. That is all there is to add the plugin.In the plugins section of your POM, add the following:.In this post some of my experiences with the plugin. Encounter difficulties keeping your dependencies and plugins up-to-date into your Maven POM file? The Versions Maven Plugin is a Maven plugin which provides you the information of which libraries could be updated.

Maven revision