[
https://issues.apache.org/jira/browse/KARAF-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103244#comment-16103244
]
Steven Spungin commented on KARAF-5274:
---------------------------------------
Exactly. Basically a way to differentiate a bundle that is 'doing something'
verses 'not doing something'.
I feel fragments that are attached and bundles that are active are the same
category, and everything else is in another. I understand why OSGi does not
use active states on bundles, but it makes the bundle:list a bit confusing.
> 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
> 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)
