Use cases I can think of (there are probably more) - use concurrent safe local repo access for all builds on a CI server without having to modify all projects - enabling extension for multi thread logging or any other feature like coloring or so across all projects I work on locally - allow different pom DSL's even when creating a new project and .mvn/extensions.xml was not yet added - easily manage version of extensions to be used across a number of projects - allow to take advantage of extensions even when you dont have full access to a project repository
I am not certain these justify the problems you mention .. which is why I think we should just let the usage of extensions get wider before we make any decisions. Manfred Graham Leggett wrote on 28.05.2015 11:21: > On 28 May 2015, at 16:58, Manfred Moser <[email protected]> wrote: > >> I think having a global config for this would be good. Personally I think >> having .m2/extensions.xml would be a good way to do it. > > Can you describe the use case? > > It seems this only makes sense if you only ever do work for one organization, > ever. As soon as you need to do work for multiple clients, or perhaps your > corporate client and an open source project, using maven becomes difficult. > > Even with a single organization having config outside the project is a right > pain. Instead of "it's maven, you know what to do", you have some weird site > specific ritual to perform, and this creates friction. > > Regards, > Graham > -- > > > --------------------------------------------------------------------- > 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]
