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

[Tomas Rohovsky (JIRA)]

Title: Message Title

Tomas Rohovsky commented on an issue   Re: Checking of API compatibility before updating of dependencies I don't much understand the APIs/IMPLs problem, because I am not familiar with META-INF/services style APIs, but I think it is better to have some compatibility checking feature than any. Contract compatibility for call sequences cannot be simply checked, it might not be even described in API documentation. So contract compatibility cannot be 100% checked. It is also not possible to check behaviour compatibility that also influences API clients. My intention of raising this feature request was to check other kind of compatibility - binary compatibility. As far as I know, it is possible to determine every binary compatibility breaking changes. I would like to implement this by my own/or lead a thesis that would deal with it. Would it ever be possible to accept a PR for this feature? Or is it completely "don't want feature" for versions-maven-plugin? 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