=?ISO-8859-1?Q?Re=3A_=5BVOTE=5D__Discontinue_Excalibur_?==?ISO-8859-1?Q?CLI__=28_was_Re=3A_=5B=A3EXCALIBUR=5D_cli_=29?=

[Leo Simons]

how about...

1) we contact the people who maintain commons-cli. We explain to them our dillemma, and that we would like to have some assurances that commons-cli will not develop more dependencies than the one on commons-lang, especially not on any package which will make application of IoC in avalon more difficult, like commons-logging in its current form.

2) if the commons-cli peeps are willing to help accomodate our IoC needs, we move our development code (like any new containers) over to use it if we haven't already.

3) For phoenix and any other existing avalon code that uses excalibur-cli, we do a point release (excalibur-cli-1.0.1) as part of our release cycle and upgrade to that in the next phoenix release.

4) After the point release of excalibur-cli we deprecate the excalibur-cli package in cvs head and have it sit around for a year or so with no new releases. If no new release proves neccessary after that and no problems have evolved with the use of commons-cli, we can completely discontinue excalibur-cli.

acceptable compromise?

cheers!

- Leo

(PS: the more [proposal]s are tagged as [vote], the more difficult it becomes to do filtering :D)



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