On Sun, Nov 24, 2013 at 8:51 AM, Thomas Neidhart
wrote:
> On 11/24/2013 02:37 PM, Emmanuel Bourg wrote:
> > Le 24/11/2013 13:09, Thomas Neidhart a écrit :
> >
> >> And merge the cli2 source into cli trunk afterwards.
> >
> > err... no, cli2 is a dead end imho. There is no point designing a new
> >
On 11/24/2013 02:37 PM, Emmanuel Bourg wrote:
> Le 24/11/2013 13:09, Thomas Neidhart a écrit :
>
>> And merge the cli2 source into cli trunk afterwards.
>
> err... no, cli2 is a dead end imho. There is no point designing a new
> incompatible API, JCommander has already filled that spot.
>
> I wo
Le 24/11/2013 13:09, Thomas Neidhart a écrit :
> And merge the cli2 source into cli trunk afterwards.
err... no, cli2 is a dead end imho. There is no point designing a new
incompatible API, JCommander has already filled that spot.
I would rather focus on incremental improvements over the current
On 11/23/2013 11:46 PM, Emmanuel Bourg wrote:
> Le 23/11/2013 16:40, Gary Gregory a écrit :
>
>> In my old code, I use [cli]. In my new code I use JCommander (also under
>> the Apache 2 license).
>>
>> [cli] really feels antiquated.
>>
>> I'd the community's thoughts on moving to a cli2 that uses
Le 23/11/2013 16:40, Gary Gregory a écrit :
> In my old code, I use [cli]. In my new code I use JCommander (also under
> the Apache 2 license).
>
> [cli] really feels antiquated.
>
> I'd the community's thoughts on moving to a cli2 that uses annotations, or
> possibly asking JCommander to join u
On 23 November 2013 15:40, Gary Gregory wrote:
> Hi All:
>
> In my old code, I use [cli]. In my new code I use JCommander (also under
> the Apache 2 license).
>
> [cli] really feels antiquated.
+1
> I'd the community's thoughts on moving to a cli2 that uses annotations
There is also the Avalon
Hi All:
In my old code, I use [cli]. In my new code I use JCommander (also under
the Apache 2 license).
[cli] really feels antiquated.
I'd the community's thoughts on moving to a cli2 that uses annotations, or
possibly asking JCommander to join us here.
Gary
--
E-Mail: garydgreg...@gmail.com
If I'm not mistaken JCommander doesn't handle concatenated options yet
(à la "tar -cxvf foo.tar"). The help message was an important feature,
Cédric Beust did really well.
Emmanuel Bourg
Le 06/06/2013 22:13, Ricardo Espírito Santo a écrit :
> Hi,
>
> Not sure if this is on the right thread but
Hi,
Not sure if this is on the right thread but I hope so.
Regarding what Simone Tripodi said in the last message: " * help usage is
handled out of the box, while in JCommander you have to handle it
manually."
I would like to state that the usage message is also handled automatically
by JCommand
Hi Gary!
they provide same basic features, but Airlines is IMHO a little
stronger in 3 points:
* drives users on pure command pattern implementation, while in
JCommander you can have just a container of passed parameters;
* simplifies the building of commands tree, such as `git remote add`
or
Hi Simo,
Thank you for the pointer. What are the pro and cons of JCommander vs.
Airline?
Gary
On Thu, Mar 7, 2013 at 1:40 AM, Simone Tripodi wrote:
> Hi Gary,
>
> there's also new guy in the town, which is called Airline[1], that
> supports the Git like commands structures. I am JCommander use
Hi Gary,
there's also new guy in the town, which is called Airline[1], that
supports the Git like commands structures. I am JCommander user as
well but in one of the last projects I plugged Airline and I really
liked it - the Help command is really straightforward! :)
Just to say what's the state
12 matches
Mail list logo
