Stephen Colebourne wrote:
<snip/>
Thus, I propose that this task is:
- started in the commons-sandbox
- uses a different package name [collgenerics]
- follows the current single jar/package structure
- no deprecated classes are ported
This sounds like the best approach to me, for the same reasons as you
outline.
Kris, are you a committer @ apache?
Yes. If others like, I can (I think) create the sandbox project once a
name is agreed upon. Should we make 3.2 the start of the branch, or is
there a reason to branch from the current state of the trunk?
Kris
Kris Nuttycombe wrote:
Speaking of porting to collections to generics, I have a bit of time
available to contribute to this effort. Could we at least create a
generics branch in SVN to get the ball rolling? This topic has been
bounced around for a long time, but the process needs to start at
some point. I realize that collections needs to be refactored into
some smaller projects, but I'm not convinced that the two tasks need
to necessarily be undertaken simultaneously. It may in fact be
simpler to generify the code in its current architecture since this
will involve less disruption to the unit tests.
Kris
Stephen Colebourne wrote:
Hi,
It would be useful to attach anything to a JIRA call, as that is an
easier worklog than email.
The biggest issue that I can see with this is that [collections] as
a project is currently at the 'full' point, and needs refactoring
into smaller units. This should probably be done as part of moving
collections to JDK1.5.
Unfortunately, [collections] has little development time available,
so just porting to generics is a big enough concept, even before
considering a new collection like Trie.
There may be another committer willing to volunteer time to this of
course...
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
