When you are coordinating a large release, this goal can help you to find stale references in dependency configuration. The versions:dependency-updates-report goal examines a project's dependency hierarchy and reports which ones have newer releases available.
![maven install without snapshot maven install without snapshot](https://cdn.ttgtmedia.com/rms/editorial/TSS_how_to_install_maven_fig3_mobile.png)
One useful goal is versions:dependency-updates-report. The Maven Versions plug-in provides goals to check your project dependencies for currency in a different ways. 3) forced Maven to evaluate the version as a string.Īn example of this effect on Maven is found in the Maven Versions plug-in. Version 1.0.9.3 should come before 1.0.10.1 and 1.0.10.2, but the unexpected fourth field (.
![maven install without snapshot maven install without snapshot](https://facingissuesonitcom.files.wordpress.com/2019/05/maven-force-update-2.jpg)
Because basic string comparison is performed on nonstandard versions, version comparison calculates the order of versions incorrectly in some cases.įor example, Maven arranges the version list in the following manner: If you use a nonstandard versioning scheme, Maven release and version plug-in goals might not yield the expected results. Maven and its core plug-ins use version comparison for a number of tasks, most importantly, the release process. If you do not follow Maven versioning standards in your project versioning scheme, then for version comparison, Maven interprets the entire version as a simple string. Identical versions with different qualifier fields are compared by using basic string comparison.
![maven install without snapshot maven install without snapshot](https://i.stack.imgur.com/zaRRt.png)
Maven's versioning scheme uses the following standards:Īll versions with a qualifier are older than the same version without a qualifier (release version).