Le dimanche 3 février 2013 11:14:03 Jason van Zyl a écrit : > I do not see what value there is in even allowing this feature to be turned > off ever. It can only cause inconsistencies. please read back the initial user complaining turning this feature off is just getting Maven 2 behaviour, even if it's not the best solution
> What Maven 2.x does is wrong because it can lead to "works for me" while not > working for anyone else. we're in perfect sync if the error meessage was clear about a solution, and gave a link to a good documentation about the possible causes and real fixes, we could avoid this flag > Why is it a good thing to let people believe they have something that works > when it doesn't work for anyone else? This is what you'll get turning this > off. it is good because Maven 3 behaves like Maven 2 (even if default Maven 3 behaviour is better) > I'm looking at the JIRA and Arnaud's explanation with the staging feature > and I think it just needs to be configured correctly. I have never had that > problem with Nexus as a staging repository is automatically added to the > group according to the staging profile and therefore the same URL for the > group works consistently. I'm not sure why you would use a profile to get > at staging repositories as you should let the repository manager deal with > that as Robert points out in the second comment. Arnaud, I'm not sure this > feature actually solves your real problem. we all know this feature does not solve the real problem: yes, it's only a workaround > >> And I'm > >> frankly tired of slapdash changes like this being made in the core > >> without > >> any discussion or review. > > > > which change are you talking about? enhanced local repository without > > really understanding or documentation, or the addition of -slrm option as > > a reasonable fix for MNG-5181, ie add an option to disable the enhanced > > local repository manager? > > Benjamin's changes are never slapdash, I'm referring to Olivier's changes. ask users if this feature is slapdash, and IMHO they will more likely say "finally". Of course, if we had a better alternative, it would be even better > I think Arnaud's case probably can be solved with a bit of re-configuration > in Nexus. Most of the users complaining either don't care about > organizational consistency and are just building for themselves, or are > trying to build offline repositories which is not Maven's primary concern. and the fact is that current error message doesn't help them understand what they are doing wrong, then help them fix it > I don't see why you would ever disable this. It covers up other problems you > have and just creates more issues. no, it does not create more issues than Maven 2 > It currently does the right thing. If an artifact is not resolvable with > the current setup you're just masking potential problems. +1 > It needs to remain off by default. Most people will never find it and likely > can't do much harm. +1 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
