You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Steven Spungin (JIRA)" <ji...@apache.org> on 2017/08/24 12:40:00 UTC
[jira] [Comment Edited] (KARAF-5274) update bundle list status for
fragments attached vs not attached
[ https://issues.apache.org/jira/browse/KARAF-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139984#comment-16139984 ]
Steven Spungin edited comment on KARAF-5274 at 8/24/17 12:39 PM:
-----------------------------------------------------------------
The Felix Webconsole uses 'fragment' instead of 'resolved' in this regard.
!Screen%20Shot%202017-08-24%20at%208.34.26%20AM.png|thumbnail!
was (Author: spungin):
The Felix Webconsole uses 'fragment' instead of 'resolved' in this regard.
!Screen%20Shot%202017-08-24%20at%208.34.26%20AM.png.jpg|thumbnail!
> update bundle list status for fragments attached vs not attached
> ----------------------------------------------------------------
>
> Key: KARAF-5274
> URL: https://issues.apache.org/jira/browse/KARAF-5274
> Project: Karaf
> Issue Type: Question
> Components: karaf-shell
> Reporter: Steven Spungin
> Priority: Minor
> Attachments: Screen Shot 2017-08-24 at 8.34.26 AM.png
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> I have a container with over 1000 bundles. There are about 25 fragments as well. I understand that a fragment never has an active state.
> When I list my bundles, I scan to see if there are any issues. I find it annoying that the fragments are listed as Resolved. I would rather see something like 'Attached'. This way I could grep the search results by resolved to find issues without having to see the fragments mixed in. Of course, if they are not attached to anything, I am OK with 'Resolved'.
> I am not suggesting to change the OSGi status, just word used in the list.
> Another solution would be to add a boolean column that displayed an 'X' on not active bundles and unattached fragments.
> I look forward to your feedback on this.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)