On Oct 23, 2011, at 1:17 PM, Mark Derricutt wrote: > Hrm - this should exactly like the behavior that the newer Aether library > -already- solves, as has done for months when you drop in the newer version. > > I know this post is more about disabling the feature, but ignoring it makes > WAY more sense IMHO. If, as you say - "Artifact A downloaded from X is not > the same thing to Maven 3 as A downloaded from Y" then the entire GAV is a > lie as it DOESN'T actually identify an artifact.
The GAV itself being a unique identifier, or GUID-like, could only be true if all artifacts came from a single source. This is not the case in practice. Peter, Paul and Mary could knowingly, or unknowingly, rebuild a library with a given GAV. If all three variants are available under different conditions you potentially have a problem. So if you use a repository manager at work and pull one variant, and then go home and pull from Maven Central, you could potentially have something different. We erred on the side of caution. A simple change, which is better than disabling this feature, would be to consider the checksum too. I'm just guessing here, but I think that's what users intuitively expect: if it comes from somewhere different but the checksum is the same it's fine, but if it is actually different than what I currently have fail, or at the very least warn me. This would not be hard to change. > > Mark > Still wanting that 3.0.4 release... > > -- > "Great artists are extremely selfish and arrogant things" — Steven Wilson, > Porcupine Tree > > > On Sun, Oct 23, 2011 at 6:19 AM, Jason van Zyl <[email protected]> wrote: > >> 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: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> 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 >> >> >> >> >> Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --------------------------------------------------------- What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham
