[mojo-dev] [jira] (MVERSIONS-267) Checking of API compatibility before updating of dependencies

[Stephen Connolly (JIRA)]

Title: Message Title

Stephen Connolly commented on an issue   Re: Checking of API compatibility before updating of dependencies To clarify the intent of the use-latest-releases style goals, the idea with those is that you would configure your pom.xml with the http://mojo.codehaus.org/versions-maven-plugin/use-latest-releases-mojo.html#includes such that only the dependencies that you control are updated. Suppose you have a project with (organization) internal dependencies that follow an independent release cycle.. You know that - because they are dependencies you can trust to follow compatibility rules - those are safe to update within certain rules. So you configure those rules and you define the scope of the goal. If you are fancy, you can even put the clirr plugin into those internal dependencies in order to ensure that when that independent release lifecycle is followed, the organizational rules on version number to backwards compatibility contract are followed. Add Comment   Mojo's Versions Maven Plugin / MVERSIONS-267 Checking of API compatibility before updating of dependencies The plugin updates dependencies no matter if APIs of the newer versions are compatible. An option that enables checking of API compatibility would be suitable. Something like --check-compatibility. An existing tool for checking of compatibility should be used for achieving of that. The options I know about: http://mojo.codehaus.org/animal-sniffer-ma... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email