[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-dev
Subject:    Re: [cli] Moving forward
From:       James Ring <sjr () jdns ! org>
Date:       2006-02-13 5:39:19
Message-ID: 200602131639.22933.sjr () jdns ! org
[Download RAW message or body]


Hi Henri and all,

On Monday 13 February 2006 16:24, Henri Yandell wrote:
> [included James in case he's not on commons-dev]
>
> So the big question is....
>
> What do we do with CLI? We have two implementations, cli1 and cli2 in
> the same build. I'm thinking we should:
>
> a) branch off a cli 1.1 based on HEAD, and delete the cli2 code from it.
> b) delete the cli 1 code from cli2 and stride forward with cli2.

This is a tough question. There has already been a release of CLI which did 
not include the CLI2 API, and there are doubtless users of CLI out there who 
will not be interested in migrating to the CLI2.

However, CLI2 has the idea of argument validators, and I think that's quite a 
handy feature of the API.

> We do need to agree that cli2 is the way forward, comparing the APIs
> to see if it feels better is one of my todo's. What do the rest of you
> think? Martin/James/anyone else?

I think you're right, we do need to compare the two APIs to make a rational 
decision. Maybe there's some scope for maintaining the current CLI API while 
merging in some of the nice validation stuff from CLI2? Whatever the choice, 
we should at least maintain a compatibility interface with this API so that 
users only have to change their code if they want to use the nice parts of 
CLI2.

> Hen

Thanks for copying me in on the discussion, I am on commons-dev also.

Looking forward to a fruitful discussion!

Regards,
James

-- 
James Ring

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]