The artifacts have an identity. It matters where the artifacts were downloaded from. Artifact A downloaded from X is not the same thing to Maven 3 as A downloaded from Y. This can happen when you flip your settings.xml to go from using a repository manager to using Maven Central directly for example.
There is currently no way to turn that off. But you can vote for the issue[1]. [1]: http://jira.codehaus.org/browse/MNG-5181 On Oct 22, 2011, at 10:05 AM, Stefan Eder wrote: > With Maven 3 dependency resolution may fail for artifacts, which have once > been fetched from a remote repository, even so they are available within the > local repository. > Guess there is a good reason for that and I would like to understand it and I > would like to know if there is a way to switch this behaviour off. > > Thanks, Stefan > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --------------------------------------------------------- In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society
