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:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>versions-maven-plugin</artifactId>
<version>2.1</version>
<configuration>
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-all</artifactId>
<version>[1.9, 2)</version>
</dependency>
<dependency>
<groupId>org.powermock</groupId>
<version>[1.4, 1.5)</version>
</dependency>
<dependency>
<artifactId>ftpserver-core</artifactId>
<version>[1.0, 2]</version>
</dependency>
</configuration>
</plugin>
Thoughts?
--
Michael Power
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
