We are just moving to JDK1.5 at work, and I too judge that the time is
about right for this. I don't know how much time I'll be able to spend
on it though. We'll have to see.
There is a clear difference of approach, however, with some factors being:
a) keep everything as close as possible to the current source (not
always achievable)
b) split into 3-5 smaller components
c) same package name or different package name
d) same project [collections] or new project
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 allows coding to start quickly, but out of everyones way. It also
then allows those of us (like me) who want to re-group the code to do so
in a sandbox environment rather than commons-proper. Getting the
promotion vote later should be no problem.
Kris, are you a committer @ apache?
Stephen
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
----- Original Message ----
From: Sam Berlin <[EMAIL PROTECTED]>
To: Jakarta Commons Developers List <[email protected]>
Cc: Roger Kapsi <[EMAIL PROTECTED]>
Sent: Wednesday, 20 September, 2006 12:42:12 AM
Subject: Contributing to Collections
Hi Folks,
I sent an email last week about contributing a Patricia tree to the
Commons
Collections project, but haven't heard back. The project is fully
voluntary, so I understand that responses may take a long time. I'd
like to
make sure that I sent the offer to the correct place, though. Is
there some
other venue I should be looking at for contributing code? Should I be
doing
this through JIRA?
To recap last week's email, Roger Kapsi & I have developed a Patricia
tree
that fits the Map & SortedMap interfaces (and can easily fit the upcoming
Java 1.6 NavigableMap), and we'd like to offer it for inclusion in
commons-collection. It's currently written for Java 1.5's generics and
licensed under the GPL, but we can easily remove the generics if required
and should likely be able to change the license if necessary.
Thanks very much,
Sam
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
