[
https://issues.apache.org/jira/browse/ACE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213552#comment-13213552
]
Paul Bakker commented on ACE-217:
---------------------------------
1) This depends. If the OBR is public I agree, you never want to throw away
anything. If the OBR is only used by ACE however, and ACE is only used to
provision your own servers, you want to have full control of it. Maven
repository managers also allow you to delete artifacts in private repositories
while this is not possible for Maven central.
2) I agree, a filter and tree view would be very helpful.
> Delete bundles and config files from the repository.
> -----------------------------------------------------
>
> Key: ACE-217
> URL: https://issues.apache.org/jira/browse/ACE-217
> Project: ACE
> Issue Type: New Feature
> Reporter: Paul Bakker
>
> If an ACE server is often updated with new versions of bundles you will end
> up with lots of obsolete bundles, which makes it hard to work with the UI.
> The UI should provide a way to completely remove bundles from the repository.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
