[
https://issues.apache.org/jira/browse/FELIX-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704704#action_12704704
]
Jamie goodyear commented on FELIX-1104:
---------------------------------------
I agree that we should ask for confirmation before stopping a system bundle.
Something I noticed when reading the patch submission is that we are starting
to collect a few classes containing '< 50'. It may be a good idea to setup a
utility class to hold the system bundle level indicator (maybe add a call to
the Util class), it would reduce the occurrence of hard coded numbers in the
package.
> 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
> Assignee: Guillaume Nodet
> Fix For: karaf-1.0.0
>
> Attachments: FELIX-1104-2.txt, FELIX-1104.txt
>
>
> Allow osgi/stop command to specify more than one bundle per command entry.
> Encountered during SMX Kernel usage:
> s...@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.
