[jira] Updated: (FELIX-1104) Allow osgi/stop command to specify more than one bundle per command entry.

["Filippo Diotalevi (JIRA)" <ji...@apache.org>]

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

Filippo Diotalevi updated FELIX-1104:
-------------------------------------

    Attachment: FELIX-1104.txt

I wanted to maintain the same user experience of the previous stop command, asking the user for confirmation to stop a bundle with startLevel < 50; so I had to do some refactoring.

- BundleCommand.java . extracted logic to check if a bundle is a system bundle and to ask user confirmation
- Util.java  added utility methods
- StopCommand.java  extends BundleSCommand instead of BundleCommand. added code to ask user confirmation to stop system bundles

> Allow osgi/stop command to specify more than one bundle per command entry.
> --------------------------------------------------------------------------
>
>                 Key: FELIX-1104
>                 URL: https://issues.apache.org/jira/browse/FELIX-1104
>             Project: Felix
>          Issue Type: Improvement
>          Components: Karaf
>         Environment: Linux
>            Reporter: Jamie goodyear
>         Attachments: FELIX-1104.txt
>
>
> Allow osgi/stop command to specify more than one bundle per command entry.
> Encountered during SMX Kernel usage:
> smx@root:osgi> stop 180 177 176 173
> ERROR CommandLineExecutionFailed: org.apache.geronimo.gshell.command.CommandException: org.apache.geronimo.gshell.clp.ProcessingException: Too many arguments: 177
> In the above example a user would have to enter 'stop 180', 'stop 177', 'stop 176', and then finally 'stop173'.  It would be nice to be able to specify a list of bundles to stop, in order, instead of having to issue a 'stop bundleId' command for each bundle.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.