[jira] (MNG-3407) improve mirroring support

["Julien Béti (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MNG-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311625#comment-311625 ] 

Julien Béti commented on MNG-3407:
----------------------------------

I just got the same issue, searching why in the hell my SNAPSHOTS were always searched in the "release" repository (and then not found...) rather than the "snapshot" one. I finally find out that the "release" one was my configured wildcard mirror....

As suggested, I changed my MRM (Archiva) to group release/snapshot repos in an "all" repo, which I use now as my wildcard mirror.

Nevertheless, I would suggest that mirror configuration should accept the releases/enable and snapshots/enable nodes, as the repository do. If it make sense, please reoppen the issue, I'm obviously not able to do it.
                
> improve mirroring support
> -------------------------
>
>                 Key: MNG-3407
>                 URL: https://jira.codehaus.org/browse/MNG-3407
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.8
>            Reporter: nicolas de loof
>            Assignee: nicolas de loof
>            Priority: Trivial
>         Attachments: message-format-mirrorOf-pattern-syntax-2.0.x.diff, message-format-mirrorOf-pattern-syntax-trunk.diff, message-format-to-mirrorOf-mirror-pattern-syntax-2.0.x.diff, mirrorOf-pattern-syntax-site.diff
>
>
> <mirrorOf>* is a helpful way to ensure maven doesn't get artifacts from the Internet in a corporate environment where we want all artifacts to be managed & backed-up.
> Usefull but limited, as this requires the mirror repository to proxy ALL repositories, beeing snapshots or not.
> Using the repository ID to build the mirror URL can make things cleaner :
> <mirror>
>          <id>*</id>
>          <url>http://mymirror/archiva/repository/{0}</url>
>          <mirrorOf>central</mirrorOf>
> </mirror>
> With such a configuration, users can setup dedicated managed repository for any public repository they want to mirror. Using archiva  makes this use case simple. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira