Hi,
I might be joining this party a little late, but what value do Commons
Collections developers feel there might be in splitting Commons
Collections into multiple JARs?
I'm all in favour of removing deprecated code, but when I think of JAR
splitting I think of what happened with Ant 1.6.x - I know plenty of
developers that now refuse to upgrade Ant. I'd be interested to hear
arguments in favour of splitting up Commons Collections. :)
Steve.
--
Stephen Smith, MEng (Wales).
http://www.stephen-smith.co.uk/
Michael Heuer wrote:
Stephen Colebourne wrote:
Plan for collections 3.2
------------------------
Agree contents
(notably, I'd like to remove BoundedBuffer)
Check bugs
Build and release in single jar format
Plan for collections 4.0
------------------------
Break collections into smaller jars
(either as one project or multiple)
Remove deprecations (maybe to a deprecated jar)
Looking ahead a bit further, at what point might the following issues
being addressed, if at all?
- bringing external jdk1.5/generics project(s) back to commons
- deprecating [collections] functor in favor of [functor] project
- resolving Collection contract violations in Bag interface
- AbstractHashedMap design improvements (Bugzilla Bug 27231)
michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
