I would like to take away some of the maintenance it comes with
upgrading dependencies. The use-latest-releases goal of the versions
plugin looks almost ideal. The problem I see is that often dependencies
will have major minor and incremental version. A change in a major
version would tend to indicate a change in the interfaces provided by
the dependency that is not backwards compatible. I want to be able to
update a dependency to the latest release version in a specific range.
That way I could configure the build so that it will always update for
minor and incremental changes but it will not update for major changes.
Since these changes would generally be backward compatible this could be
automated to upgrade a dependency every new release.
I imagine this kind of thing would be configured like:
To unsubscribe from this list, please visit:
No I am definitely looking for use-latest-releases. Assume that I am using something like slf4j-api, at a particular release level. I want to automatically upgrade as they fix bugs. But I do not want to automatically upgrade to a release that is backwards incompatible. Thus I want to define the range of acceptable releases.
If I was current dependent on:
I might know that when this project makes backward incompatible changes they bump their minor number. So I would not want to upgrade to version 1.7.x automatically. Hence I would set my configuration to use the version range [1.6,1.7). That would mean everything starting at 1.6 and ending just before 1.7. My current version (1.6.3) would fit in this range. But if you check online there are also release versions: 1.6.4, 1.6.5, 1.6.6, 1.7.0, 1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5. Without a version range the use-latest-release would take me up to 1.7.5. But I do not want to upgrade to a 1.7.x version. I want to upgrade to a 1.6.x version, specifically I want it to upgrade to 1.6.6.
On 10/15/2013 11:43 AM, Arnout Engelen wrote:
|Free forum by Nabble||Edit this page|