Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D412B200CCC for ; Fri, 21 Jul 2017 17:52:52 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D2BCB16B2F5; Fri, 21 Jul 2017 15:52:52 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 15B4616A1B1 for ; Fri, 21 Jul 2017 17:52:51 +0200 (CEST) Received: (qmail 80880 invoked by uid 500); 21 Jul 2017 15:52:51 -0000 Mailing-List: contact user-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@karaf.apache.org Delivered-To: mailing list user@karaf.apache.org Received: (qmail 80871 invoked by uid 99); 21 Jul 2017 15:52:51 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Jul 2017 15:52:51 +0000 Received: from mail-yw0-f174.google.com (mail-yw0-f174.google.com [209.85.161.174]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id BFD711A0029 for ; Fri, 21 Jul 2017 15:52:50 +0000 (UTC) Received: by mail-yw0-f174.google.com with SMTP id a12so25981100ywh.3 for ; Fri, 21 Jul 2017 08:52:50 -0700 (PDT) X-Gm-Message-State: AIVw110zRPfhzEcAxn9JrCTuU2Ah9G8WFNo7TusU0YDGPcr03wjI9Ad3 tJ+65x/SEdgDHIW36uMaFlH217enMQ== X-Received: by 10.129.136.132 with SMTP id y126mr6344455ywf.223.1500652369354; Fri, 21 Jul 2017 08:52:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.13.213.137 with HTTP; Fri, 21 Jul 2017 08:52:28 -0700 (PDT) In-Reply-To: <1083807026.1445591.1500650829762@webmail.123-reg.co.uk> References: <1781731028.1418776.1500630824787@webmail.123-reg.co.uk> <1cb26f7e-f178-4aef-9109-1cfb26fde2be@nanthrax.net> <1716460468.1421923.1500632841770@webmail.123-reg.co.uk> <38a642b1-ea49-225f-ebaf-1070e779f5a0@die-schneider.net> <1083807026.1445591.1500650829762@webmail.123-reg.co.uk> From: Guillaume Nodet Date: Fri, 21 Jul 2017 17:52:28 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Writing commands for karaf shell. To: user , tom@quarendon.net Content-Type: multipart/alternative; boundary="001a114f16946854eb0554d5dbb5" archived-at: Fri, 21 Jul 2017 15:52:53 -0000 --001a114f16946854eb0554d5dbb5 Content-Type: text/plain; charset="UTF-8" Right now, stick with the Karaf annotations if you want to deploy your commands in Karaf. It works and it's supported. My previous comment was more a reply to Christian about what needs to be done to support gogo commands in the future. 2017-07-21 17:27 GMT+02:00 : > > If you look at Karaf >= 4.1.x, a bunch of commands are not coming from > > Karaf anymore, but from Gogo or JLine. I moved them when working on the > > gogo / jline3 integration. The main point that was blocking imho is that > > they did not have completion support. With the new fully scripted > > completion system from gogo-jline, gogo commands can have full > completion, > > so I don't see any blocking points anymore. It's just about tracking > > commands and registering them in the karaf shell. > > I'm sorry, but I don't really understand what you're saying. You're > talking about impediments to making changes to Karaf? Or how I go about > writing commands? > Sorry, just not following. > > Fundamentally, should commands that I write using apache felix gogo > command features such as the Parameter and Description annotations, and the > CommandService interface work? Or if I want to do something other than a > simple "hello world", do I need to work out how to use the karaf shell from > within bndtools so that I can write commands using the Karaf command > framework? > > Thanks. > -- ------------------------ Guillaume Nodet --001a114f16946854eb0554d5dbb5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Right now, stick with the Karaf annotations if you want to= deploy your commands in Karaf.=C2=A0 It works and it's supported. =C2= =A0
My previous comment was more a reply to Christian about what needs = to be done to support gogo commands in the future.

2017-07-21 17:27 GMT+02:00 <tom@qua= rendon.net>:
> If you look at Karaf >=3D 4.1.x, a bunch of commands are not com= ing from
> Karaf anymore, but from Gogo or JLine.=C2=A0 I moved them when working= on the
> gogo / jline3 integration.=C2=A0 The main point that was blocking imho= is that
> they did not have completion support.=C2=A0 With the new fully scripte= d
> completion system from gogo-jline, gogo commands can have full complet= ion,
> so I don't see any blocking points anymore.=C2=A0 It's just ab= out tracking
> commands and registering them in the karaf shell.

I'm sorry, but I don't really understand what you're say= ing. You're talking about impediments to making changes to Karaf? Or ho= w I go about writing commands?
Sorry, just not following.

Fundamentally, should commands that I write using apache felix gogo command= features such as the Parameter and Description annotations, and the Comman= dService interface work? Or if I want to do something other than a simple &= quot;hello world", do I need to work out how to use the karaf shell fr= om within bndtools so that I can write commands using the Karaf command fra= mework?

Thanks.



--
------------------------
Gui= llaume Nodet

--001a114f16946854eb0554d5dbb5--