commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berin Loritsch" <blorit...@apache.org>
Subject FW: [CLI] Making Option Extensible
Date Wed, 24 Jul 2002 17:22:59 GMT


> -----Original Message-----
> From: Berin Loritsch [mailto:bloritsch@apache.org] 
> Sent: Wednesday, July 24, 2002 1:22 PM
> To: 'Avalon Developers List'
> Subject: RE: [CLI] Making Option Extensible
> 
> 
> > From: Henri Yandell [mailto:bayard@generationjava.com]
> > 
> > On 24 Jul 2002, Leo Simons wrote:
> > 
> > > > To Avaloners: I propose to deprecate the whole Avalon 
> CLI package
> > > > and port all programs using it to the Commons version.
> > >
> > > I won't vote till it is clear what the implications will
> > be; which is
> > > exactly the point of this thread innit?
> > >
> > > I'd like guarantees that:
> > >
> > > - the move will be transparant to end users (ie no change in CLI
> > > options
> > > themselves)
> > >
> > 
> > How do you propose this is tested?
> > 
> > Can Avalon classes be changed over to CLI and tests run, or
> > would Avalon supply example arguments and Commons would show 
> > that these examples are properly parsed with a generic test class?
> 
> 
> Avalon CLI does have a testcase that we can adapt for Commons CLI.
> For compatibility, the parser type has to be the GnuParser.  If it
> passes that test, then we are good to go.
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:avalon-dev-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <mailto:avalon-dev-help@jakarta.apache.org>
> 


--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message