Hi Tom, Tom Eugelink wrote:
> I know Maven version management can be, ah, challenging, so I stick to > Maven compatible versioning. Maybe not to the deepest level (1.0.0-b01), > but surely in a very common accepted style (1.0). I am not having any > problems with Maven using the wrong versions. > > My question is with how to tell Maven two releases are no longer > compatible. So if one dependency uses 1.x and the other uses 2.x, and 2.x > is "declared" not backwards compatible to 1.x, then Maven should either: > 1. report a build error on a version conflict 2. or include both versions > of the artifact. 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? - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
