I have a console command implementation in place that is based on Apache Gogo
Shell, making use of "org.apache.felix.service.command.*". Unfortunately,
the commands are not recognized in Apache Karaf 3.x. I had a look to your
command implementations which are based on the artifcat
"org.apache.karaf
Hi Achim,
The problem was, that the the use of relativ paths in
...
The context while testing is another than in project. So never an exchache was
sent.
Phiuu...
Thanks for helping!
Christian
Christian Eugster
Docuteam GmbH
Langacker 16
Postfach
CH-5405 Baden-Dättwil
+41
Hi,
what do you mean by non Karaf command ? You mean running directly in
Felix or running "outside" of OSGi ?
Regards
JB
On 03/14/2015 10:21 AM, Herr-Herner wrote:
I have a console command implementation in place that is based on Apache Gogo
Shell, making use of "org.apache.felix.service.com
Yes... Directly in Equinox or Apache Felix.
--
View this message in context:
http://karaf.922171.n3.nabble.com/Creating-Apache-Karaf-console-commands-tp4039023p4039031.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Hi,
you can implement Felix Gogo command (even if I would prefer the K3/K4
approach in term of features).
By the way, the command-archetype provided by Karaf give you a skeleton
to create Karaf commands.
Regards
JB
On 03/14/2015 12:46 PM, Herr-Herner wrote:
Yes... Directly in Equinox or A
Hi,
Great that it worked now.
Regards, Achim
sent from mobile device
Am 14.03.2015 11:22 schrieb "Christian Eugster" :
> Hi Achim,
>
> The problem was, that the the use of relativ paths in
>
>
>
> ...
>
>
> The context while testing is another than in project. So never an exchache
> was sent
Ok... I checked the Apache SCR shell integration which uses Gogo. I missed
that the SCR feature installs an external command handler based on the Karaf
shell.
So, if I got you right, the recommended way is to use the karaf shell and
not gogo for custom extensions, right?
--
View this message in
Correct.
Regards
JB
On 03/14/2015 04:02 PM, Herr-Herner wrote:
Ok... I checked the Apache SCR shell integration which uses Gogo. I missed
that the SCR feature installs an external command handler based on the Karaf
shell.
So, if I got you right, the recommended way is to use the karaf shell an
What I'm suggesting is to decouple the logfile location, as done with
other kinds of locations such as:
${karaf.home}
${karaf.base}
${karaf.data}
${karaf.etc}
and introduce an additional ${karaf.log} ($KARAF_LOG)
Currently, "${karaf.data}/log" (or $KARAF_DATA/log) occurs in several
places: