This should probably move to the dev list, but if we're considering POM changes in a future Maven version, should a <repository> element become become part of the dependency declaration?
Altho if we're going that far I'd also like to see <repositories/> actually be REMOVED from the pom, and moved to ~/.m2/settings.xml along side the mirrors, with the <repository/> part of the GA(R)V being required -if- the artifact is from a custom declared repository. This would certainly speed up a lot of builds that (#(*$#(* declare N-repositories in the pom causes maven to walk thru each of them when trying to find something. -- "Great artists are extremely selfish and arrogant things" — Steven Wilson, Porcupine Tree On Mon, Oct 24, 2011 at 10:45 AM, Jason van Zyl <[email protected]> wrote: > I wasn't implying anything about the quality of Maven Central. It's > orthogonal to this argument which is to say the GAV could only work as a > unique identifier if there was one source, or all sources were identical. > The quality of the contents is irrelevant. > > The quality of the content is a driving factor in creating variants which I > think is your point. >
