because if you want global extensions, there is a mechanism that exists for a long time: put jar files in lib/ext
the new .mvn/extensions.xml feature is really about permitting non-global extensions, to ease per-project tests before making the extensions global (and if the extension is a strong requirement and not only an enhancement, add it to the documentation for the team to make sure it doesn't work with stock Maven but configured one) so, it's not a bug, it's really a feature :) Regards, Hervé Le mercredi 27 mai 2015 13:52:18 Jordan Zimmerman a écrit : > What is the reason that .mvn/extensions.xml has to be added to every > project? It would be much more useful to add it globally in the .m2 > directory. If I want to standardize, say, on Groovy polyglot I don’t want > to have to have every developer in our org remember to add the extension to > every project. That would be a big pain. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
