Thanks Richard, I really appreciate it. 2010/11/22 Richard S. Hall <[email protected]>: > I just spent a minute creating a patch for the old shell to register a > command to bridge to Gogo, it is attached. This is just a quick and dirty > example. > > So, if you really need to use some old shell commands within Gogo, just > apply this patch to the source of the old shell and deploy it and activate > it. Then you should be able to run old commands like this: > > bridge ps -s > > The "bridge" command is a Gogo command, everything else is passed to the > shell service. > > -> richard > > On 11/22/10 9:34, Richard S. Hall wrote: >> >> On 11/22/10 3:46, Felix Meschberger wrote: >>> >>> Hi, >>> >>> There are currently no scr commands for the gogo shell. This is >>> currently just a planned feature ... >> >> It's actually pretty easy to convert commands from the old shell to >> Gogo...I converted all the built-in commands and never ran into an issue >> (once we got the approach figured out). >> >> We could also create a single bundle that created a bridge from the old >> shell commands to Gogo too, for those holdovers. >> >> -> richard >> >>> Regards >>> Felix >>> >>> Am Montag, den 22.11.2010, 16:28 +0800 schrieb Harry chen: >>>> >>>> Hi, >>>> >>>> I am getting start to learn about OSGI with Felix. As I know in Felix >>>> Distribution 2.0, I can use "scr list, scr enable" to start a component >>>> define by Declarative Service, "scr info" to get the detail of >>>> specific component. >>>> But when it changed to gogo shell in Felix Distribution 3.0. Is there >>>> any >>>> command can describle component information in gogo shell? Or did i >>>> miss some bundle which is necessary. Thank you. >>>> >>>> Sincerely >>>> Roger Chen >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
