It was the gogo shell conversation that I couldn't remember and I had included but I think Christian and Guillaume picked up on it and seem to be working on a way forward. I like the karaf shell. It has autocomplete, history, coloring and several other features that the gogo shell was missing. I think karaf and gogo shell split because one of the libraries changed their license. I knew Guilluame was working on a new version of the shell that used a custom version of jline that fixed the licensing issue but there was another blocker in that the new version required java8. Java8 should not be a problem with karaf after 4.0.4 because it is needed for the new jetty but it may still be an issue with felix. I was hoping that if in the new karaf upgrade the karaf shell moved to use Guillaume's new code then some of the changes could be merged back into the gogo shell. As far as I can tell there has been very little work on the gogo shell recently but it would be nice if that changed. I cannot speak to the issues Christian has with the karaf shell but they seem to have optional fixes if you are willing to accept the draw backs.
David Daniel On 2015-12-01 21:22, David Leangen wrote: >> I can't remember and don't understand all the conversation from the emails >> below > > It started from a comment I made: > > For Karaf commands, also at first I was not happy that it forced me to > decide "either or" simple gogo commands or Karaf commands. However, > the Karaf commands really are nice. I think somebody should push to have > completers and all the other nice stuff added to the OSGi spec. It was in the context of "standard" vs. "non-standard" OSGi. Karaf seems to be doing both, but for good reasons. There are still many holes in OSGi. Whether they are left there on purpose to allow people the freedom to design their own solutions, or they are there simply because nobody has developed the solution yet, I cannot say. Karaf is clearly pushing the boundaries on the runtime front. Pushing the boundaries is great, but I think we need to be careful when things get too far. I really like Karaf commands, but they seem to have become "non-standard", which is something I usually try to avoid when possible. To me, the ideal solution is to take the great things about Karaf commands (help system, completers...) and try to introduce them into the OSGi spec. Has anybody considered this? Cheers, =David
