It seems that you are interested in experimenting with a new scope and possibly a new implementation for the collections.primitives stuff. My suggestion then is this:
A) Go ahead with a commons-collections release including collections.primtives.* B) Continue experimenting with the new primitives component in the sandbox, perhaps seeding it with a repackaged version of collections.primitives. C) If at some future point we decide that collections.primitives.* is a better fit elsewhere, we deprecate collections.primitives.* in one release, say Collections 4.0 (roughly coincident with a release of the alternative packaging and/or implementation of that functionality), and remove it in a following release, say Collections 5.0. Holding back on stable, release-ready, unit- and field-tested code so that we can play around with alternative implementations or groupings seems unnecessary when there are backward and forward compatible options available. - Rod <http://radio.weblogs.com/0122027/> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
