[
https://issues.apache.org/jira/browse/MRM-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Stockhammer updated MRM-1146:
------------------------------------
Fix Version/s: (was: 2.2.2)
3.0.0
> [Virtual repo browse] An artifact is immediately proxied from the remote repo
> (assuming a proxy connector is configured for the first repo) if the artifact
> doesn't exist in the first repo but exists in the second repo in the group
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRM-1146
> URL: https://issues.apache.org/jira/browse/MRM-1146
> Project: Archiva
> Issue Type: Bug
> Components: WebDAV Interface
> Affects Versions: 1.2-M1, 1.2
> Reporter: Maria Odea Ching
> Fix For: 3.0.0
>
> Attachments: MRM-1146.patch
>
>
> I have two repositories with ids 'first' and 'second'. Repository 'first' is
> configured to proxy the central repository. In 'first', I have
> commons-lang/commons-lang/2.4/commons-lang-2.4.jar and in 'second', I have
> commons-lang/commons-lang/2.3/commons-lang-2.3.jar. I created a group with id
> 'all' which has these 2 repositories under that group. When I browse the
> group 'all', I see both commons-lang-2.3 and commons-lang-2.4. Now when I
> clicked/downloaded commons-lang-2.3.jar, I noticed that commons-lang-2.3.jar
> was proxied from the remote repo and created in repository 'first'.
> The artifact that should have been served is the one from 'second' repository
> and not proxied from 'central' via the 'first' repository.
> I only verified this in 1.2-M1 and in trunk. I didn't check if this exists as
> well in the 1.1 series.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
