Re: [VOTE] Discontinue Excalibur CLI ( was Re: [?EXCALIBUR] cli)

[Stephen McConnell]

Noel J. Bergman wrote:

Are there any *technical* reasons why Commons CLI is impossible to use
as a CLI package for us?

Seems to me that Peter Donald raised an issues that still needs to be
verified, corrected, or voted upon as insignificant:

Peter Donald raised two objections: (1) that Commons CLI is not under our control, and (2) that depedencies that Commons CLI has on other projects.

As far as "control" is concerned - I consider "out-of-our-control" to be a plus. Command line management is not something with the scope Avalon. The fact that a commons solution exists which is consitent with Excalibur CLI is a real plus. It means that we can confidently release control.

It is also coupled to several dependencies last time I checked.

Apparently, he feels that these additional dependencies prevent Commons CLI
from being a migration path.

Personally, I haven't a clue what dependencies or their significance. Just
noting the specific outstanding issue.

Commons CLI has a dependency on common.lang (used for String to type conversion) and commons.lang has no dependencies. If you don't need command line argument string value to type conversion then you don't need to worry about commons.lang. But anyway, I don't see that a dependency to commons.lang as a problem.

I remain in favour of giving Excalibur CLI a free ticket to Florida.

Cheers, Steve.

--

Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]