Oh, I've seen your mail to late. Thanks for sharing, cause as one can see here, it is actually possible to live without the gogo-shell. Lot's of projects did work on some sort of shell, cause it fit into their system, it does fit their needs.
But what are we going to do about this, maybe we should make them be based on gogo-shell also? regards, Achim P.S. beware this text might contain sarcasm and or irony, please be careful while reading. 2014-02-27 3:35 GMT+01:00 includeeasy <flo...@gmail.com>: > There is some projects that already have quite a lot of function. > > 1. aeshell (http://aeshell.github.io),it is used in jboss forge. > Features: > Line editing > History (search, persistence) > Completion > Masking > Paste buffer > Emacs and Vi editing mode > Support all POSIX OS and Windows > Support out and error streams > Command line parser > Aliases > Undo and Redo > Pipeline > Redirect > ++ > 2. Other tools list as belows,can we reference one of it? > jopt-simple (http://pholser.github.io/jopt-simple/) > JArgs > Jakarta Commons CLI > TE-Code has a command line parsing library. > argparser > Java port of GNU getopt > Args4J > JSAP > CLAJR > CmdLn > JewelCli > JCommando > parse-cmd > JCommander > > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Ideas-about-karaf-and-gogo-commands-tp4031934p4031964.html > Sent from the Karaf - Dev mailing list archive at Nabble.com. > -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/>
