Tom Eugelink wrote: > >> 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.
If my app did not use the methods that have been removed, it is - at least for my application. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
