Well.. let’s stay with airline if you don’t see any upcoming problems with the dead looking airline project. I would like to have some of the open issues of airline in our cli, but it’s more a nice to have and no showstopper.
> On 31 Oct 2016, at 20:51, Clebert Suconic <[email protected]> wrote: > > it would need some heavy refactoring... it's not a direct replacement. > > Airline supports commands and parameters... > > That way you can add a bunch of classes, and airline could figure out between: > > ./artemis data > ./artemis run... > > etc... > > JComander from what I just looked it only supports the parameters. > > > Airline is apache license, if the project becomes abandonware we could > fork it and add it to our modules. It's pretty small anyways. > > > On Mon, Oct 31, 2016 at 3:01 PM, Christopher Shannon > <[email protected]> wrote: >> JCommander would be a good alternative but not sure we'd gain much by >> switching if airline works for now. >> >> On Mon, Oct 31, 2016 at 12:04 PM, Clebert Suconic <[email protected] >>> wrote: >> >>> It's something simple that does the job we need.. but if anyone have >>> any suggestion? >>> >>> On Mon, Oct 31, 2016 at 11:50 AM, Bennet Schulz <[email protected]> >>> wrote: >>>> Hi there, >>>> >>>> I just took a look at the airline project on github: >>> https://github.com/airlift/airline <https://github.com/airlift/airline> >>> and it seems to be dead. The last commit was in October the 11th in 2015 >>> and there are lots of open and unanswered pull requests and issues. >>>> Is it a good idea to stay with airline for future releases or should be >>> think about replacing it with another CLI lib? >>>> >>>> best, >>>> Bennet >>> >>> >>> >>> -- >>> Clebert Suconic >>> > > > > -- > Clebert Suconic
