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]
