[
http://jira.codehaus.org/browse/MRM-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186800#action_186800
]
Maria Odea Ching commented on MRM-1232:
---------------------------------------
I was able to retrieve the artifact by reversing the order of 'releases' and
'internal' in the group. It seems that the repo group returns an error based on
the encountered error from the last repository in the group.
Since 'releases' is secured, it returned an unauthorized exception when maven
first requested the artifact anonymously. When maven got this, it requested the
artifact again but this time passing the credentials.
> Unable to get artifacts from repositories which requires Repository Manager
> role using repository group
> -------------------------------------------------------------------------------------------------------
>
> Key: MRM-1232
> URL: http://jira.codehaus.org/browse/MRM-1232
> Project: Archiva
> Issue Type: Bug
> Components: WebDAV interface
> Affects Versions: 1.2.1
> Reporter: Maria Odea Ching
> Assignee: Maria Odea Ching
> Fix For: 1.2.2
>
>
> To reproduce:
> # Create managed repository 'releases'
> # Create a new user account with the following credentials
> #* username: newuser
> #* password: pass1
> # Assign Repository Manager role for 'releases' repository to newuser
> # Deploy a test artifact to 'releases' repository. Make sure that the
> credentials are configured in settings.xml
> # Create a new repository group named 'internal.group'
> # Add the 'releases' repository and the pre-configured 'internal' repository
> to 'internal.group'
> # Add the following configuration to your settings.xml:
> {code}
> <mirrors>
> <mirror>
> <id>internal.group</id>
> <name>Local Mirror</name>
> <url>http://localhost:8080/archiva/repository/internal.group</url>
> <mirrorOf>*</mirrorOf>
> </mirror>
> <mirrors>
> <servers>
> <server>
> <id>internal.group</id>
> <username>newuser</username>
> <password>pass1</password>
> </server>
> </server>
> {code}
> # Build a project with a dependency on the test artifact you deploy in step
> 4. The build would fail with unable to resolve artifact ... error.
> # Edit guest account and assign Repository Observer role for repository
> 'releases'
> # Build the project again. You would get a successful build.
--
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
