Michael McCallum wrote:
On Thu, 14 Aug 2008 00:09:59 Brian E. Fox wrote:
I have to disagree here: developers should not care what repositories
they have, or what dependency plugin shows them. They should, instead,
simply say what they want - and get it. That is why, imho, the core,
including dependency resolution, should be smarter :)
I agree. The problem with excluding repos to try and influence your
dependency resolution is that snapshots may already be in your local repo.
Since it hits the local first, you can't effectively disable the snapshots
at that point.
the local repos should not be the cache of remote repos thats a design flaw...
the local repo should be treated like all others...
Michael - good point! In Mercury I am replacing dumb repository, that
only knows pathOf(GAV) with an active repository that has strictly GAV
interface and deals with storage details inside. And I allow as many as
you wish "local" repos - it's a matter of configuration. Local repos
have isLocal() set to true and they are searched first.
This allows, for instance, having "local releases" and "local snaphots"
repos, while still supporting good old "local cache" paradigm. But that
is another discussion.. - please see children of
http://docs.codehaus.org/x/D4CnBQ
Oleg
