You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Philip K. Warren (JIRA)" <ji...@codehaus.org> on 2010/09/24 23:47:36 UTC
[jira] Created: (MRM-1423) Blacklisting doesn't update existing
metadata files
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
[jira] Commented: (MRM-1423) Blacklisting doesn't update existing
metadata files
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236430#action_236430 ]
Wendy Smoak commented on MRM-1423:
----------------------------------
Assuming Archiva does 'remember' where it got things from, what would be the purpose of just removing an item from the metadata?
(At a guess: are you thinking this would make the artifact unavailable for download?)
I'm wondering if there is an underlying problem here that might be solved some other way.
> 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
[jira] Commented: (MRM-1423) Blacklisting doesn't update existing
metadata files
Posted by "Philip K. Warren (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MRM-1423) Blacklisting doesn't remove artifacts
that were previously proxied
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1423:
------------------------------
Fix Version/s: Backlog
Issue Type: New Feature (was: Bug)
Summary: Blacklisting doesn't remove artifacts that were previously proxied (was: Blacklisting doesn't update existing metadata files)
I'm putting this in as a new feature. I don't think blacklisting is intended to affect the managed repository, just the proxy connection - but I agree there should be a better way to connect these two behaviours.
> Blacklisting doesn't remove artifacts that were previously proxied
> ------------------------------------------------------------------
>
> Key: MRM-1423
> URL: http://jira.codehaus.org/browse/MRM-1423
> Project: Archiva
> Issue Type: New Feature
> Components: remote proxy
> Affects Versions: 1.3.1
> Reporter: Philip K. Warren
> Fix For: Backlog
>
>
> 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
[jira] Commented: (MRM-1423) Blacklisting doesn't update existing
metadata files
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236427#action_236427 ]
Wendy Smoak commented on MRM-1423:
----------------------------------
I don't think Archiva "remembers" where it proxied something from.
I am also not sure that configuration changes should be retroactive.
That is, once you blacklist something, Archiva will not do further downloads, but it won't go back and remove what it has already downloaded.
If you determine that there are 'bad' artifacts coming from a certain repo you can use the delete feature to get rid of them.
> 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
[jira] Commented: (MRM-1423) Blacklisting doesn't update existing
metadata files
Posted by "Philip K. Warren (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236429#action_236429 ]
Philip K. Warren commented on MRM-1423:
---------------------------------------
The metadata files have the ID of the proxy repository in the name (maven-metadata-<id>.xml). Then all of the proxied repository files metadata is merged into one metadata file. I agree that it would be difficult however to remove artifacts, but it shouldn't be as difficult to regenerate the metadata files.
> 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
[jira] Commented: (MRM-1423) Blacklisting doesn't update existing
metadata files
Posted by "Philip K. Warren (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236829#action_236829 ]
Philip K. Warren commented on MRM-1423:
---------------------------------------
Yes that is a better summary for what I was looking for.
> 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
[jira] Commented: (MRM-1423) Blacklisting doesn't update existing
metadata files
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236433#action_236433 ]
Wendy Smoak commented on MRM-1423:
----------------------------------
Would a better summary be, "Blacklisting doesn't remove artifacts that were previously proxied" ?
It sounds like that's what you want.
(Removing something from the metadata won't prevent someone from accessing the artifact. It might not show up in browse or search, and it would mess up plugin and snapshot retrieval, but normal released artifacts would still work fine as far as 'mvn install' goes.)
> 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