In regards to #2 the '-s' start flag operates on all the bundles listed, it would appear to be fare game to set a list of bundles to a particular start level as well. The 'help' entry should have appropriate notice of how it operates of course.
--Jamie On Wed, Apr 16, 2014 at 8:05 PM, Jon Anstey <[email protected]> wrote: > I've opened https://issues.apache.org/jira/browse/KARAF-2917 to track #1. I > would find this useful too... or maybe we need a "sed" command in Karaf :-) > > Not sure we should implement #2 as bundle:install operates on a bundle list > so the args should applicable to the whole bundle list IMO. > > > On Tue, Apr 15, 2014 at 12:58 PM, rich.peters <[email protected]> wrote: >> >> Hi, >> >> we have had a hard time working around installing some updates to osgi >> bundles that our security required we make. There is currently not an >> easy >> way to get the bundle id of an arbitrary package. >> >> >> Life would be a lot easier if there were two new features: >> >> >> 1. There was an osgi command to query the bundle id of a package name >> in >> the maven format: >> >> osgi:bundle org.springframework/spring-core/3.1.4.RELEASE >> >> currently there is no way to get the bundle id of a package easily >> >> >> >> 2. The osgi:install command accepted a bundle bundle-level as an >> optional >> parameter (as in the osgi:bundle-level command) >> >> if you do 1. you dont absolutely need this, but it would be >> convenient >> >> >> >> These two features would make scripting upgrades easier >> >> >> >> thanks >> >> Rich >> >> >> >> -- >> View this message in context: >> http://karaf.922171.n3.nabble.com/Karaf-console-command-enhancements-for-osgi-tp4032774.html >> Sent from the Karaf - User mailing list archive at Nabble.com. > > > > > -- > Cheers, > Jon > --------------- > Red Hat, Inc. > Email: [email protected] > Web: http://redhat.com > Twitter: jon_anstey > Blog: http://janstey.blogspot.com > Author of Camel in Action: http://manning.com/ibsen
