Maven resolves dependencies under the (rightful) assumption that a higher version is 100% backwards compatible to an earlier release, and therefor picks the highest requires version of a dependency. But once every so often a library should be purged, things cannot be @depricated forever.
Is it possible to tell Maven a library is not backwards compatible anymore? I usually use a major version increment for such steps (e.g. 1.x becomes 2.x). But even specifying ranges "[1.0,1.999]" combined with "[2.0,2.999]" do not cause an error of some kind, but simply resolve to 2.x. Kind regards, Tom --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
