Re: Pain with MNG-5181 (_maven.repositories)

2013-01-31 Thread Andreas Gudian
Am Freitag, 1. Februar 2013 schrieb Jason van Zyl : > > On Jan 31, 2013, at 7:13 PM, Arnaud Héritier > > > wrote: > > > Hi Olivier, > > > > Thx a lot for the fix. It will help a lot the community. > > But from my point of view it's perhaps not yet enough. > > We should : > > 1/ change the de

Re: Pain with MNG-5181 (_maven.repositories)

2013-01-31 Thread Benson Margulies
On Fri, Feb 1, 2013 at 3:47 AM, Jason van Zyl wrote: > > On Jan 31, 2013, at 7:13 PM, Arnaud Héritier wrote: > >> Hi Olivier, >> >> Thx a lot for the fix. It will help a lot the community. >> But from my point of view it's perhaps not yet enough. >> We should : >> 1/ change the default behavi

Re: Pain with MNG-5181 (_maven.repositories)

2013-01-31 Thread Jason van Zyl
On Jan 31, 2013, at 7:13 PM, Arnaud Héritier wrote: > Hi Olivier, > > Thx a lot for the fix. It will help a lot the community. > But from my point of view it's perhaps not yet enough. > We should : > 1/ change the default behavior to deactivate this control which is > difficult to understan

Cutting a release

2013-01-31 Thread Jason van Zyl
I have not had a lot of time to work on the class loader isolation but in light of these two problems: WAGON-372 WAGON-383 I would say a Wagon release should be cut, and we live without the logging classloader isolation and get the release out. I am going to do a full graph analysis on Central

Re: Pain with MNG-5181 (_maven.repositories)

2013-01-31 Thread Wayne Fay
> 1/ change the default behavior to deactivate this control which is > difficult to understand > 2/ change the error message when this control is activated to clearly > explain that the problem comes from the unavailability of the artifact on > its original remote repo. > > For me 1/ is manda

Re: Pain with MNG-5181 (_maven.repositories)

2013-01-31 Thread Arnaud Héritier
Hi Olivier, Thx a lot for the fix. It will help a lot the community. But from my point of view it's perhaps not yet enough. We should : 1/ change the default behavior to deactivate this control which is difficult to understand 2/ change the error message when this control is activated to

Re: Pain with MNG-5181 (_maven.repositories)

2013-01-31 Thread Olivier Lamy
I have pushed a fix for that. Now you can desactivate the enhanced local repository using: * new cli option: -slrm,--simple-local-repository-manager * or in MAVEN_OPTS: -Dmaven.simpleLocalRepoMan=true will be available for testing here https://builds.apache.org/job/maven-3.x/ with build #368 201

Re: Pain with MNG-5181 (_maven.repositories)

2013-01-31 Thread Jörg Hohwiller
Hi Arnaud, > +1 to consider the current behavior as a bug. > We should be able to deactivate it easily (and perhaps to have it off by > default to activate it only on CI servers) :) > and we should take care to have > a real error message explaining the issue and not a classical dependency > no

Re: [VOTE] Plugins parent 24 and Shared parent 19

2013-01-31 Thread Anders Hammar
0 It would have been good to get v1.8 of m-invoker-p in maven-plugins while we're at it. /Anders On Wed, Jan 30, 2013 at 12:40 AM, Olivier Lamy wrote: > Hi, > I'd like to release Plugins parent 24 and Shared parent 19. > Staging repository: > https://repository.apache.org/content/repositories

Re: [SCM] GitExe : no fetch after push ?

2013-01-31 Thread Frédéric Camblor
@Robert : I'm not using maven-release-plugin, that's for a jenkins plugin @Olivier thanks for the insights I'll try to work on a PR, but I need some piece of advice on the "better way" to resolve my problem, by staying in