commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Keyes <j...@mac.com>
Subject RE: [CLI] Making Option Extensible
Date Wed, 24 Jul 2002 16:10:16 GMT
On Wed, 2002-07-24 at 17:02, Berin Loritsch wrote:
> > From: John Keyes [mailto:jbjk@mac.com] 
> > 
> > On Wed, 2002-07-24 at 16:27, Nicola Ken Barozzi wrote:
> > <snip>
> > > 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.
> > I wish that someone from Avalon would step forward ;)
> 
> So Nicola and I don't count?
(It did end with a smiley;)
What I meant was if there is another issue other than the
GNU support could someone please let us know.

> > <snip>
> > > 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.
> > This would be great!  Should this wait until we release
> > a version of CLI or is the current development snapshot 
> > sufficient.
> 
> We need a release first.  If Commons CLI can produce compatible
> user interface (i.e. scripts that pass options to your Java
> project don't have to change), then Let's release Commons CLI
> and we can deprecate Avalon CLI.

I don't get the i.e. part of that sentence, what scripts?  Could
you show an example of this?

Cheers,
-John K



--
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