You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "b v j (JIRA)" <ji...@codehaus.org> on 2008/12/27 04:14:19 UTC
[jira] Created: (MRM-1053) Search and Destroy artifacts according
to originating remote proxy
Search and Destroy artifacts according to originating remote proxy
------------------------------------------------------------------
Key: MRM-1053
URL: http://jira.codehaus.org/browse/MRM-1053
Project: Archiva
Issue Type: New Feature
Components: search
Reporter: b v j
It would be helpful to query artifacts based on the source/originating remote proxy. It would also be helpful if the associated artifacts could be deleted.
--
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-1053) Search and Destroy artifacts according
to originating remote proxy
Posted by "b v j (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163355#action_163355 ]
b v j commented on MRM-1053:
----------------------------
>> wouldn't it be better to just separate your hosted repos to match the remote ones so that you can dump the whole repo?
That's a good option. My Archiva managed repos are limited to the two defaults, and I should divide them according to the nature of the remotes. I'd still like to link multiple remotes to a single managed repo, and also have the means to flush the repo of artifacts provided by a particular remote. If I dump the entire managed repo, I might have a problem repopulating it if some remotes are unavailable at that time.
> Search and Destroy artifacts according to originating remote proxy
> ------------------------------------------------------------------
>
> Key: MRM-1053
> URL: http://jira.codehaus.org/browse/MRM-1053
> Project: Archiva
> Issue Type: New Feature
> Components: search
> Reporter: b v j
>
> It would be helpful to query artifacts based on the source/originating remote proxy. It would also be helpful if the associated artifacts could be deleted.
--
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-1053) Search and Destroy artifacts according
to originating remote proxy
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159279#action_159279 ]
Wendy Smoak commented on MRM-1053:
----------------------------------
Can you explain a bit more about what you want Archiva to do? It sounds like at least two different features.
Or... do you want the equivalent of rsyncing a remote repo?
> Search and Destroy artifacts according to originating remote proxy
> ------------------------------------------------------------------
>
> Key: MRM-1053
> URL: http://jira.codehaus.org/browse/MRM-1053
> Project: Archiva
> Issue Type: New Feature
> Components: search
> Reporter: b v j
>
> It would be helpful to query artifacts based on the source/originating remote proxy. It would also be helpful if the associated artifacts could be deleted.
--
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-1053) Search and Destroy artifacts according
to originating remote proxy
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1053:
------------------------------
Fix Version/s: 1.x
> Search and Destroy artifacts according to originating remote proxy
> ------------------------------------------------------------------
>
> Key: MRM-1053
> URL: http://jira.codehaus.org/browse/MRM-1053
> Project: Archiva
> Issue Type: New Feature
> Components: search
> Reporter: b v j
> Fix For: 1.x
>
>
> It would be helpful to query artifacts based on the source/originating remote proxy. It would also be helpful if the associated artifacts could be deleted.
--
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-1053) Search and Destroy artifacts according
to originating remote proxy
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163176#action_163176 ]
Brett Porter commented on MRM-1053:
-----------------------------------
wouldn't it be better to just separate your hosted repos to match the remote ones so that you can dump the whole repo?
> Search and Destroy artifacts according to originating remote proxy
> ------------------------------------------------------------------
>
> Key: MRM-1053
> URL: http://jira.codehaus.org/browse/MRM-1053
> Project: Archiva
> Issue Type: New Feature
> Components: search
> Reporter: b v j
>
> It would be helpful to query artifacts based on the source/originating remote proxy. It would also be helpful if the associated artifacts could be deleted.
--
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-1053) Search and Destroy artifacts according
to originating remote proxy
Posted by "b v j (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163354#action_163354 ]
b v j commented on MRM-1053:
----------------------------
>> Can you explain a bit more about what you want Archiva to do? It sounds like at least two different features.
I have multiple remote repositories tied via proxy connectors to my "Archiva Managed Internal Repository". It's working very well. Similarly, I have a few linked to the Snapshot repo.
On more than one occasion, I needed to change the remote repo for a given set of artifacts. My preference would be to first unlink the old remote repo, and purge the Internal repo of any artifacts fetched therefrom. Next, I'd link to the new repo containing the artifacts once served by the old repo.
For auditing purpose, it would also be helpful to know what repos provided which artifacts.
> Search and Destroy artifacts according to originating remote proxy
> ------------------------------------------------------------------
>
> Key: MRM-1053
> URL: http://jira.codehaus.org/browse/MRM-1053
> Project: Archiva
> Issue Type: New Feature
> Components: search
> Reporter: b v j
>
> It would be helpful to query artifacts based on the source/originating remote proxy. It would also be helpful if the associated artifacts could be deleted.
--
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