commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <>
Subject Re: [CLI] future
Date Sun, 24 Nov 2013 14:49:27 GMT
On Sun, Nov 24, 2013 at 8:51 AM, Thomas Neidhart

> 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 would rather focus on incremental improvements over the current API.
> well, I never looked at cli2, but I thought substantial work has gone
> into it on which we could continue.
> Some time ago, I played around with various cli implementations,
> including jcommander, args4j and airline.
> All of them have their strengths but also limitations.
> I ended up using jcommander but did the help printing myself via
> reflection to better align it with the gnu style help which I wanted to
> mimick.
> So I think there is potential to come up with a cli library that really
> combines the strength of all the other competitors and is still very
> flexible to use. But it depends if there is really a community interest
> for this as there are already so many alternatives available that are
> available right now and people are using them.

I took a brief look at airline as well and picked JCommander. For
JCommander, feedback, progress on issues and new features is glacial.

I'd love to have a JCommander-like component in [cli2 or 3] so we can all
drive it faster, better, stronger ;) Doing 'better' than JCommander will be
subjective but we can make the features broader, like the help style


> Thomas
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

E-Mail: |
Java Persistence with Hibernate, Second Edition<>
JUnit in Action, Second Edition <>
Spring Batch in Action <>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message