[
https://jira.codehaus.org/browse/MRM-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308459#comment-308459
]
Olivier Lamy commented on MRM-1658:
-----------------------------------
is that still valid ?
I see some changes in Maven2RepositoryStorage regarding that.
> Archiva not honoring managed configuration to get meta or others artifacts
> --------------------------------------------------------------------------
>
> Key: MRM-1658
> URL: https://jira.codehaus.org/browse/MRM-1658
> Project: Archiva
> Issue Type: Test
> Affects Versions: 1.4-M3
> Environment: tomcat 7 fedora 17
> Reporter: Eric Barboni
> Fix For: Backlog
>
> Attachments: m2rs.patch
>
>
> Well, was looking for lots of log because I find archiva a bit slow.
> 2 managed (internal and company-internal) only release (3 remotes)
> 2 managed (snap and company-internal) only snap (12-remotes)
> Trying to compile archiva, looking for apache9-pom
> it fails on the 12 remotes only snap.
> I attach a test case copy pasted from Maven2RepositoryMetadataResolverTestand
> expecting an exception.
> Don't want to disturb build before having feedback it's a bug.
--
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
