Am Freitag, 1. Februar 2013 schrieb Jason van Zyl : > > On Jan 31, 2013, at 7:13 PM, Arnaud Héritier > <[email protected]<javascript:;>> > 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 understand > > I disagree. We may want to change it slightly but it's only a problem for > people who flip between Maven a repository manager and without but it's to > ensure the identity of a component. I haven't seen a huge number of > complaints. I do not want to turn this off. Improve it, sure, but turning > it off by default I believe is not the right thing to do. > > How about turning it into a warning by default and only fail if you enable some meaningful option (or implicitly in some plugins such as the release plugin).
But I must admit that I don't really have a use case in mind where failing is crucial. > > 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]<javascript:;>> > 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] <javascript:;>>: > >>> 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] <javascript:;> > >> For additional commands, e-mail: [email protected]<javascript:;> > >> > >> > > > > > > -- > > ----- > > Arnaud Héritier > > http://aheritier.net > > Mail/GTalk: aheritier AT gmail DOT com > > Twitter/Skype : aheritier > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder & CTO, Sonatype > Founder, Apache Maven > http://twitter.com/jvanzyl > --------------------------------------------------------- > > Our achievements speak for themselves. What we have to keep track > of are our failures, discouragements and doubts. We tend to forget > the past difficulties, the many false starts, and the painful > groping. We see our past achievements as the end result of a > clean forward thrust, and our present difficulties as > signs of decline and decay. > > -- Eric Hoffer, Reflections on the Human Condition > > > > > >
