You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Maria Odea Ching (JIRA)" <ji...@codehaus.org> on 2009/08/19 13:10:59 UTC

[jira] Updated: (MRM-1146) [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

     [ http://jira.codehaus.org/browse/MRM-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching updated MRM-1146:
----------------------------------

    Fix Version/s:     (was: 1.2.2)
                   1.2.3

> [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: http://jira.codehaus.org/browse/MRM-1146
>             Project: Archiva
>          Issue Type: Bug
>          Components: WebDAV interface
>    Affects Versions: 1.2-M1, 1.2
>            Reporter: Maria Odea Ching
>             Fix For: 1.2.3
>
>
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira