James Strachan wrote:
> From: "Nicola Ken Barozzi" <[EMAIL PROTECTED]>
>
>>John Keyes wrote:
>>...
>>
>>>I was thinking about how this would affect the current
>>>implementation and I winced at all of the changes to the
>>>constructors and the addOption methods.
>>
>>Have you looked at the Avalon CLI?
>>We want to move it to Commons, this can be a good opportunity to compare
>>approaches and point of integration.
>
>
> RTM (as you often like to say ;-)
>
> http://jakarta.apache.org/commons/cli/
I did read it, and I have already told Avaloners that commons CLI takes
also from the Avalon code.
Someone from Avalon told me that the Avalon one had something more, and
viceversa.
Since I cannot read all the tons of lines of code we have, it would be
more constructive if you gave a hand instead of pointing to the manual.
We are not CLI users, we are part of the same project, man.
> CLI is already based on ideas from CLI in Avalon. Pretty much CLI started
> out as a merge of werken.opt and CLI, admittedly using most of werken.opt,
> then later on John integrated his Optz code base into commons-cli too. So I
> think that the current commons-cli codebase pretty much has the best bits of
> all 3, werken.opt, Avalon CLI and Optz.
>
> Though if anyone can find any feature/option thats in Avalon CLI and not in
> commons-cli just say and we can patch it.
I know the refrain ;-P
To Avaloners: I propose to deprecate the whole Avalon CLI package and
port all programs using it to the Commons version.
I can do the conversion of the Cocoon Main.java class, but don't know
about others.
?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
