[jira] [Resolved] (FELIX-5001) scr:list Gogo command should display component configurations

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FELIX-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved FELIX-5001.
-------------------------------------
    Resolution: Fixed

I've changed the gogo command to list configurations instead of descriptions
The info command can now be used with either a component name or a configuration ID
Fixed some descriptions for the shell commands and the config command (flush was missing)
Rev 1695222

> scr:list Gogo command should display component configurations
> -------------------------------------------------------------
>
>                 Key: FELIX-5001
>                 URL: https://issues.apache.org/jira/browse/FELIX-5001
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-2.0.0
>            Reporter: Neil Bartlett
>            Assignee: Carsten Ziegeler
>            Priority: Critical
>             Fix For: scr-2.0.2
>
>
> The gogo command scr:list has changed drastically since version 1.8.2 and is now unusable. The component IDs are not displayed and so there is no way for the user to pass this ID to the scr:info command.
> Here is the current output:
> {noformat}
> g! scr:list
>  Name  BundleId DefaultEnabled
> [org.example.exchange.orderentry.OrderEntry] [  11] [true]
> [org.example.exchange.prices.feed] [   2] [true]
> [org.example.osgi.exchange.impl.ExchangeImpl] [   2] [true]
> {noformat}
> For reference, here was the much more useful output from 1.8.2:
> {noformat}
> g! scr:list
>  Id   State BundleId Name
> [   0] [active      ] [   2] org.example.osgi.exchange.impl.ExchangeImpl
> [   1] [active      ] [   2] org.example.exchange.prices.feed
> [   2] [active      ] [  11] org.example.exchange.orderentry.OrderEntry
> [   3] [active      ] [   2] org.example.exchange.prices.feed
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)