[
http://jira.codehaus.org/browse/MRM-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236432#action_236432
]
Philip K. Warren commented on MRM-1423:
---------------------------------------
I was thinking that this would no longer provide an artifact which was hosted
on the blacklisted portion of the proxy repository.
If there is a better way to handle this sort of issue (removing a feature
manually), then I'm ok with that approach. I just thought it would make more
sense if you wouldn't have to go through and manually clean up the repository
if we had enough information to "purge" the blacklisted portions of the
repository automatically.
> Blacklisting doesn't update existing metadata files
> ---------------------------------------------------
>
> Key: MRM-1423
> URL: http://jira.codehaus.org/browse/MRM-1423
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.3.1
> Reporter: Philip K. Warren
>
> When using the remote proxy support, I found that updating proxies to add
> blacklisted items didn't trigger any sort of update of the metadata in the
> repository. I was expecting that any references to metadata or previously
> downloaded artifacts from the blacklisted portion of the repository would be
> removed.
> For example, create two remote repositories - one for Maven central and one
> for JBoss public. Then run 'mvn archetype:generate' against Archiva. It will
> download the archetype plug-in metadata from both central and JBoss (JBoss
> has SNAPSHOT versions).
> Then configure a blacklist of 'org/apache/maven/**' on the JBoss repository.
> Expected behavior:
> 1) Metadata should be rebuilt to remove any references to artifacts in the
> blacklisted portion of the JBoss repository.
> Actual behavior:
> 1) Metadata remains for the blacklisted paths.
> The only way I could determine how to fix this was to remove this portion of
> Archiva and manually trigger a re-indexing of the repository.
--
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
