[
https://jira.codehaus.org/browse/MVERSIONS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Walling updated MVERSIONS-183:
----------------------------------
Attachment: AbsoluteLatestReleasesMojo.java
AbsoluteLatestReleasesMojo would be one way to address this. It calculates the
absolute most recent release version and updates to it. This also handles the
cases where the most recent release is earlier than the most recent snapshot.
> neither use-latest-releases nor use-releases can skip to latest releas in
> certain circumstances
> -----------------------------------------------------------------------------------------------
>
> Key: MVERSIONS-183
> URL: https://jira.codehaus.org/browse/MVERSIONS-183
> Project: Maven 2.x Versions Plugin
> Issue Type: Bug
> Affects Versions: 1.3.1
> Reporter: Don Walling
> Attachments: AbsoluteLatestReleasesMojo.java
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
