commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Russel Winder <rus...@russel.org.uk>
Subject Re: [cli] What are the current status for CLI 2.0?
Date Sat, 27 Oct 2007 07:25:57 GMT
Hen,

On Sat, 2007-10-27 at 00:08 -0700, Henri Yandell wrote:
> On 10/26/07, Russel Winder <russel@russel.org.uk> wrote:
> >
> > On Fri, 2007-10-26 at 15:58 -0700, s29752-commonsdev@yahoo.com wrote:
> > > Brian, thank you for the information.  I have checked the JIRA issues.
> > > It seems to me that CLI 2 is kind of working and there is no big
> > > problems.  Do you agree?  Or I better use CLI 1.1?
> > >
> > > Actually, I am thinking about use CLI 2 for my application and work on
> > > CLI 2 at the same time.  It seems to me that the CLI 2 committers are
> > > not currently active.  So it is hard to work on it.  Is there anything
> > > we can do except for waiting?
> 
> In the absence of anyone else, I'll look at Brian's CLI2 patches
> tomorrow and get them moving along.

That would be great.

I need to try the experiment of converting Groovy and Gant from CLI-1.0
to CLI-2.0 -- it only requires changes in a few places but I haven't had
time over the last 12 weeks to tackle this.  Hopefully next month I
will.

> > Many weeks ago, I reported that the Groovy project is having to stay
> > with CLI 1.0 since despite all the great bug fixes and effort that Henri
> > and Brian put in to create the CLI 1.1 distribution, there are some
> > showstopper bugs that got introduced.  I put one test case onto JIRA but
> > have not had time since to investigate the issues myself and it seems
> > no-one else has either.
> 
> Yup, Brian and I both recently changed jobs :) Looks like things are
> getting a bit more active again now.

Hopefully the jobs are both more fun and better paid :-)

Groovy and Gant may well soon shrug off the shackles of Java 1.4 and
leap into the new annotated world of Java 5.0 :-) This may mean that
annotation-based systems rather than builder-based systems might come
into play.  Having said this, a builder-based approach actually fits
better with the total Groovy infrastructure, e.g. CliBuilder -- which is
a thin adapter to Commons-CLI.

My feeling is therefore that it would be better to get Groovy working
with a post CLI-1.0, working CLI before considering any other options.
If CLI-2.x is the way forward that would be good, even though it needs
more work to port the Groovy code base.

Thanks.

-- 
Russel.
====================================================
Dr Russel Winder                       t: +44 20 7585 2200
41 Buckmaster Road               m: +44 7770 465 077
London SW11 1EN, UK              w: http://www.russel.org.uk/

Mime
View raw message