maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Eugelink <>
Subject Re: breaking backwards compatibility
Date Wed, 13 Apr 2011 10:10:59 GMT

> What means "not compatible" for a single artifact? If my application only
> uses a constant defined in some class, the dependency is only incompatible
> if this constant is no longer available, has a different type or a value
> that causes a failure situation in my own app.
> You can define real incompatibility only from the consumer side. So what
> could Maven actually report by default?

It is a real world scenario that at some time a library is purged; that @deprecated methods
are actually deleted, that API's are refactored. Such a version is no longer backwards compatible.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message