It's intentional that all repos in the group get consulted and this
shouldn't be a problem - but you also mention proxying. If requests
are going out of Archiva by a proxy request you can control them by
using the whitelist and blacklist on the proxy connector.
- Brett
On 31/03/2009, at 4:11 AM, Emerson Cargnin wrote:
>
> Hi Guys
>
> I had the issue below with 1.1, and in my case I needed to filter the
> artifacts so that a repository group would get the artifact from the
> first
> in the group that would have it available, without asking for the
> rest.
> maria had mentioned that this behaviour could be made configurable
> by group.
>
> I just installed version 1.2, is there any progress on this on this
> version?
>
> regards
> Emerson
>
>
> Emerson Cargnin wrote:
>>
>> Hi Guys
>>
>> I had an issue that I was trying to use a virtual repository to
>> access a
>> legacy maven1 repository which had a lot of public jars besides
>> private
>> ones. I wanted to use the virtual repo to get only the needed ones
>> from
>> this legacy and proxy it on archiva, so that I would easily know
>> which are
>> the jars that we are public available but we were addressing wrong.
>> It happens that this way things are done now will ask the same
>> resource to
>> all repositories that are part of the group.
>> As maria mention in the user maillist, it would be great if this
>> functionality could be configurable.
>>
>> thanks
>> Emerson cargnin
>>
>>
>
> --
> View this message in context:
http://www.nabble.com/wrong-metadatas-tp18360791p22788034.html> Sent from the archiva-dev mailing list archive at Nabble.com.
>
