Peter Donald wrote:
This is not a reason IMHO. Xerces is, Xalan is, QDox is, HttpClient is, as well as many other jars we depend on. Wanting to control everything has brought us to a big excalibur with packages that have directly nothing to do with Avalon, and CLI is one of them.On Thu, 30 Jan 2003 12:23, Stephen McConnell wrote:Yep the Commons CLI is beyond our control.As far as I can tel the Excalibur CLI package should be depricated in favour of the Commons CLI package. Any objections?
It is also coupled to several dependencies last time I checked. No need to deprecate something that works and is used when there is no migration path.Commons CLI is our migration path. They seem to be very receptive, have included features we needed, and are now evaluating a patch from Nick Chalko of Krysalis to be totally reflective. I encouraged him to work with them instead of doing it on his own, and I do the same here.
Are there any *technical* reasons why Commons CLI is impossible to use as a CLI package for us?
Besides, on http://jakarta.apache.org/commons/cli/ I read:
"
CLI : Command Line Interface
The CLI library provides a simple and easy to use API for working with the command line arguments and options.
CLI is based on ideas and code from
* werken.opt by Bob Mcwhirter
* The cli package in Avalon Excalibur by Peter Donald
* Optz by John Keyes
"
For these reasons, and for the fact that we had already informally decided AFAIK to switch to the Commons version, I as us to vote.
Do you want that we discuntinue Excalibur CLI in favor of Jakarta Commons CLI?
+1
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
