Re: [VOTE] Deprecate 2 more Excalibur Projects

[Leo Simons]

Peter Donald wrote:

On Fri, 21 Feb 2003 05:27, Berin Loritsch wrote:

I would like to push to vote to deprecate Excalibur CLI in
favor of Commons CLI.

No need to deprecate something that works and is mor eloosely coupled than the alternative. However it may be best to move it out of Avalon.

I think our main need wrt deprecation is to point out to our users that avalon as a project would like to stop investing energy into the maintainance of these packages, while still wanting to provide a good upgrade path 'n stuff.

Moving the package out is an alternative that accomplishes that as well.

My preference for a move would be to move to merge with commons-cli :D

Also, vote to deprecate Excalibur IO in favor of
Commons IO

+1 from me

Would it not be wise to wait till it is at least in commons proper

yep. I think it is good policy to not use or depend on commons-sandbox components (any sandbox code) in non-sandbox avalon code. Since I/O is released, we shouldn't deprecate until a viable alternative is available, just like with the ECM/fortress scheme.

cheers,

- Leo



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