You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by "Paul Bakker (Created) (JIRA)" <ji...@apache.org> on 2012/02/22 00:04:49 UTC
[jira] [Created] (ACE-217) Delete bundles and config files from the
repository.
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
[jira] [Commented] (ACE-217) Delete bundles and config files from
the repository.
Posted by "Marcel Offermans (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213128#comment-13213128 ]
Marcel Offermans commented on ACE-217:
--------------------------------------
There's two parts to this story:
1) The OBR. This is a repository where, similar to a Maven repository, you probably never ever want to throw away artifacts because they might still be used (somewhere, in an old version).
2) The artifacts column. Here I would say if nobody uses an artifact, you should be able to delete it (or rather, its metadata). We also have the option here to display the artifacts in a tree view (similar to what BndTools does) to give a better overview. And/or we could add filters to hide unused artifacts.
> 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
[jira] [Commented] (ACE-217) Delete bundles and config files from
the repository.
Posted by "Marcel Offermans (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213127#comment-13213127 ]
Marcel Offermans commented on ACE-217:
--------------------------------------
There's two parts to this story:
1) The OBR. This is a repository where, similar to a Maven repository, you probably never ever want to throw away artifacts because they might still be used (somewhere, in an old version).
2) The artifacts column. Here I would say if nobody uses an artifact, you should be able to delete it (or rather, its metadata). We also have the option here to display the artifacts in a tree view (similar to what BndTools does) to give a better overview. And/or we could add filters to hide unused artifacts.
> 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
[jira] [Updated] (ACE-217) Delete bundles and config files from the
repository.
Posted by "Marcel Offermans (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans updated ACE-217:
---------------------------------
Comment: was deleted
(was: There's two parts to this story:
1) The OBR. This is a repository where, similar to a Maven repository, you probably never ever want to throw away artifacts because they might still be used (somewhere, in an old version).
2) The artifacts column. Here I would say if nobody uses an artifact, you should be able to delete it (or rather, its metadata). We also have the option here to display the artifacts in a tree view (similar to what BndTools does) to give a better overview. And/or we could add filters to hide unused artifacts.)
> 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
[jira] [Commented] (ACE-217) Delete bundles and config files from
the repository.
Posted by "Paul Bakker (Commented) (JIRA)" <ji...@apache.org>.
[ 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