Berin Loritsch wrote:
I will go through the process of committing the full deprecation on Avalon collections and move it to Commons. We can get rid of that dependency completely from our CVS. The question is, when do we want to remove the dead code with a CVS delete?
Some questions:
1. has the Excalibur Collections even been officially released?
2. do we know of anyone using it
3. what is the impact on an Excalibur Collections user to migrate?
Some suggestions:
1. Insead of deleting put README in place that states clearly that the package is dead
2. Move the package into something like jakarta-avalon-excalibur/subset/collections
3. Delete the build file so as to prevent inadvertent CVS builds
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:mcconnell@;osm.net
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
