Le mardi 24 mars 2015 13:09:03 Tibor Digana a écrit : > Why the Maven core isn't plugable via SPI, for instance the class > ComparableVersion? this was an old dream request, but when I tried, I found it would not make sense if the config had to be done in pom.xml And having the config in setting.xml of lib/ext was too much, since this would change the comparaison algorithm for every Maven run
now that we have .mvn to load extension on specific projects, making the comparison algorithm would be feasible even if I'm not convinced it is useful... > It's a class which does not need any Maven API and no extension plugin. > We may refuse spending our efforts on fixing debatable issues which would be > good for both parties Maven developers and users. Changing the current > behavior may allow reporting new JIRA issues due to breaking current > behavior. The SPI would simplify our situation, wouldn't it? now, such a SPI will require a really good documentation, since without good documentation, it's only more complex code that nobody will be able to extend > > ComparableVersion class was just an example, maybe trivial, but the idea is > obvious. for sure, .mvn gives new opportunities: we'll need to find a way to document extension points, or Maven core will become even more complex wihtout anybody being able to really take advantage of it (or only a happy few who were there at the beginning) Regards, Hervé > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Re-Version-ranges-and-snapshots-tp5825997p > 5830193.html Sent from the Maven Developers mailing list archive at > Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
