Not sure if the projects would agree. The commands are already working
but without completion it would just be half the fun.
And besides the people who are happy without completion probably just
never used karaf before :-)
So yes the first step is to make the commands at least visible. So the
commands completer needs to show them. This is pretty easy to achieve.
I would still like to improve it more if I have the time.
I think a good side effect of making gogo commands better supported in
karaf is that maybe some users that only know gogo with their own
commands till now might give karaf a spin and stay.
Christian
On 25.02.2014 14:55, Achim Nierbeck wrote:
Thanks for sharing this.
Now you are missing the KISS part here :)
6. Use Gogo commands
Make sure gogo commands not only are executable in Karaf Shell but are also
visible. (that's the only thing missing right now)
So any project that really needs to support both world does need to reduce
to the minimum possible for it's commands.
And here we go: you have every use-case satisfied.
Every project that will rely on Karaf "only" is free to use the full
features of Karaf.
All others will have to live with the "minimum" set, which just lacks the
completion.
I guess they can live without, cause everyone else in the std. gogo
eco-system seems to be quite happy with it.
regards, Achim
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com