How do I implement a console extension without blueprint?
I created a BundleActivator and tried to publish the service
OsgiCommandSupport guessing that would cause the system to pickup the new
shell command, but I was wrong.
thanks,
Adam
On Fri, Jan 21, 2011 at 22:47, Adam Crain acr...@greenenergycorp.com
wrote:
How do I implement a console extension without blueprint?
I created a BundleActivator and tried to publish the service
OsgiCommandSupport guessing that would cause the system to pickup the
new
shell command, but I
On Sun, Jan 23, 2011 at 1:44 PM, Guillaume Nodet gno...@gmail.com wrote:
The namespace you use is wrong, it should be
http://karaf.apache.org/xmlns/shell/v1.0.0
On Sun, Jan 23, 2011 at 19:18, Adam Crain acr...@greenenergycorp.com
wrote:
Thanks for the tips. I stripped everything down
Searching through Karaf source, I noticed that OsgiCommandSupport has a
getBundleContext method. I can just use that to see if the services I need
are there when the command is invoked. Is this considered bad practice?
On Sun, Jan 23, 2011 at 2:21 PM, Adam Crain acr...@greenenergycorp.comwrote
Hi,
First off, awesome project! We're doing an open source release of an
automation platform redistributing karaf in 5 days!
For the purpose of continuous integration, has anyone had luck scripting
against the Karaf sshd shell?
Basically, we have to boot strap our system using a couple of our
the version in Karaf/pom.xml and recompile.
Kind regards, Andreas
On May 26, 2011 6:44 PM, Adam Crain acr...@greenenergycorp.com wrote:
Hi,
I'm working on some experimental changes to pax-logging to support the
optional SLF4J LocationAwareLogger specification, but I'm having workflow
