Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.3.1
-
Fix Version/s: None
-
Labels:None
-
Number of attachments :
Description
In the case where a dependency has the following versions:
1.1.0-snapshot
1.2.0
1.3.0-snapshot
In the above case there is no 1.1.0 release. If a pom is currently using the 1.1.0-snapshot dependency, and the desire is to use the 1.2.0 release, there is not a way for the versions plugin to do the update. The versions:use-releases goal will fail to the 1.1.0-snapshot dependency to 1.1.0 since 1.1.0 does not exist. The versions:use-latest-releases goal will fail because it only updates dependencies from one release version to another and will skip over this dependency since it is a snapshot. There isn't a goal in the versions plugin that will find the latest release of an older snapshot.
AbsoluteLatestReleasesMojo.java is a modification to UseLatestReleasesMojo.java that coerces snapshot versions into release versions and then does the search for newer release artifacts. This would be one way to solve the bug.
Another approach might be to add a flag to UseLatestReleasesMojo.java