Hi, > 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.
FWIW, in general, I agree 100%. One of the beautiful things about Maven is that for every project, you can: $ git clone git://github.com/myorg/myproj $ cd myproj $ mvn And good things happen! So awesome! As soon as you also have to start tweaking ~/.m2/settings.xml or settings-security.xml or extensions.xml or whatever, the beauty is gone... Regards, Curtis On Thu, May 28, 2015 at 1:21 PM, Graham Leggett <minf...@sharp.fm> wrote: > On 28 May 2015, at 16:58, Manfred Moser <manf...@mosabuam.com> 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: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
