Le 10/10/2013 13:47, Ate Douma a écrit : > While doing this might be somewhat automated, sure, I still would not > favor this. > I think it tries to solve more of a perceived than an actual problem.
I'm afraid this is more than a perceived issue, the plexus-container example given by Jörg is a very good one. Pushing drastically incompatible versions to Maven Central is not a good service for the users. I think my suggestion is a good compromise, otherwise the die-hard compatibility defenders here will never agree to publish incompatible artifacts to Maven Central. > And it is not convenient for the experimental end-users either, because > they most definitely will HAVE to modify their code (manually). I agree this is annoying, but this has to be balanced with the annoyance of dealing with incompatible dependencies (for example, components depending on different versions of BouncyCastle). It's easy to rename an import in your code compared to fixing a jar hell situation. Emmanuel Bourg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
