not sure
> > how that would happen. It seems like this data needs to be stored in the
> > repo itself and then cached in the local repo. Otherwise someone would
> > have to provide a redirection service which isn't feasible for all
> > repos.
> >
> >
repo itself and then cached in the local repo. Otherwise someone would
> have to provide a redirection service which isn't feasible for all
> repos.
>
>
>
>
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Sunday, March 16, 20
ch 16, 2008 7:06 PM
To: Maven Developers List
Subject: Maven's future repository support
Forking the other thread.
Maven still needs to work properly without a repository manager (even
if it is a good practice to use one). In my opinion, that means:
- proper unique identifiers for repos
That sounds good to me, and I see where the identifiers have come in;
I think you could do without them though, and just use the repository
URI as the identifier :-
For 'external' mirrors, accessed directly and not through a repo manager:
Say you have repo1.maven.org/maven2, and global mirrors of
Forking the other thread.
Maven still needs to work properly without a repository manager (even
if it is a good practice to use one). In my opinion, that means:
- proper unique identifiers for repositories (my preference would
actually be to control this by group ID, but I see too many counte
