no time to work on it for the moment: my list is already full for at least a week or 2 to be able to release Maven 3.1-alpha-1 and everything necessary
but I probably will work with you on this topic after that: I don't know if I will agree with everything, but having some new ideas and proof of concept seems a right approach Regards, Hervé Le mercredi 10 avril 2013 12:27:43 Andrei Pozolotin a écrit : > *Maven Developers* > > 1) This is a formal request to resolve long standing version range > policy problem in maven, > expressed for example in the following ticket: > http://jira.codehaus.org/browse/MNG-3092 > > THE PROBLEM: LACK OF VERSION RANGE POLICY. > > 2) I there are no better ideas, I suggest Maven to adopt OSGI > Semantic Version Guidelines. > https://github.com/barchart/barchart-version-tester/wiki/Version-Policy > > 3) I have working prototype based on maven 3.0.4 with back port of > aether 0.9.0.M2 > specifically applied to karaf use case, which could be generalized. > https://github.com/barchart/barchart-maven-karaf-plugin > > 4) there is an Aries version check plugin, that shows generic java > binary compatibility checks > which should be part of the new maven semantic version contract. > https://github.com/apache/aries/tree/trunk/versioning > > Thank you, > > Andrei --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
