[
http://jira.codehaus.org/browse/MRM-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136974#action_136974
]
Maria Odea Ching commented on MRM-694:
--------------------------------------
Hmm.. maybe this happened because of the browsing history stored in the
browser?
I was able to replicate this when I previously logged in as 'admin' and browsed
the repo group, then logged out. When I accessed the repo group, I was still
able to browse everything and when I tried accessing the repo which the guest
user has read access, I was prompted for authentication. But when I cleared the
browsing history and tried the repo group url again, I was only able to see the
repositories which guest has read access to.
> Virtual repositories or repository grouping
> -------------------------------------------
>
> Key: MRM-694
> URL: http://jira.codehaus.org/browse/MRM-694
> Project: Archiva
> Issue Type: New Feature
> Components: repository interface
> Reporter: Maria Odea Ching
> Assignee: Maria Odea Ching
> Fix For: 1.1
>
> Attachments: MRM-694-archiva-configuration.patch,
> MRM-694-archiva-webapp.patch, MRM-694-archiva-webdav.patch,
> MRM-694-web-interface.patch
>
>
> A number of managed repositories can be grouped together with that group
> having only one url. So you only need to specify that url in the settings.xml
> file and when Archiva receives a request via that url, it would look for that
> artifact from the repositories belonging to that group.
> More details are dicussed here:
> http://www.nabble.com/Archiva-1.1-Roadmap-td15262645.html#a15263879
--
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
