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 clearly explain that the problem comes from the unavailability of the artifact on its original remote repo.
For me 1/ is mandatory and 2/ a nice to have WDYT ? On Fri, Feb 1, 2013 at 12:53 AM, Olivier Lamy <[email protected]> wrote: > 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 > > > 2013/1/31 Jörg Hohwiller <[email protected]>: > > 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 > >> not found while the artifact is in the local repo. > > > > This is exactly filed here: > > http://jira.codehaus.org/browse/MNG-5185 > > > >> > >> Arnaud > > Cheers > > Jörg > > > > -- > > If know-how becomes know-where, then knowledge gets nowhere. > > [Jörg Hohwiller] > > > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- ----- Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
