commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <flame...@gmail.com>
Subject [collections] merging collections
Date Sat, 12 Sep 2009 09:00:03 GMT
On Fri, Sep 11, 2009 at 8:58 AM, Matt Benson<gudnabrsam@yahoo.com> wrote:
>
>
> --- On Fri, 9/11/09, Henri Yandell <flamefew@gmail.com> wrote:
>
>> From: Henri Yandell <flamefew@gmail.com>
>> Subject: Re: [collections] generics WAS [jira] Commented: (COLLECTIONS-110)  Support
parametized classes with commons.collections.
>> To: "Commons Developers List" <dev@commons.apache.org>
>> Date: Friday, September 11, 2009, 10:33 AM
>> On Fri, Sep 11, 2009 at 7:17 AM, Matt
>> Benson<gudnabrsam@yahoo.com>
>> wrote:
>> >
>> >
>> >> Henri Yandell commented on COLLECTIONS-110:
>> >> -------------------------------------------
>> >>
>> >> In the absence of anyone being active on a rewrite
>> of
>> >> Collections for generics, I agree with James that
>> you should
>> >> look elsewhere for an active project.
>> >>
>> >> I'm happy to help out with Collections 3.x bugs,
>> and have
>> >> done a fair bit towards 3.3, but I've neither the
>> time to
>> >> release 3.3 nor inclination to drive a redesigned
>> 4.0.
>> >>
>> >> This is someday going to drive me to want to add
>> some of
>> >> the core most basic pieces of Collections to Lang
>> :) I
>> >> suspect that might be after a look at
>> google-collections to
>> >> make sure it's not something they have. Parts of
>> >> ComparatorUtils, CollectionUtils, MapUtils and
>> SetUtils.
>> >
>> > Most of the work here has been done in the
>> collections_jdk5_branch.  Are we ready for these
>> > changes to be merged back to trunk, and is there
>> anyone who considers his svn-fu to be top-
>> > notch for the purposes of a large and complex merge?
>>  If we answer the first question "yes,"
>> > maybe we should start a thread for the second
>> question, as my attempts to merge were less
>> > than fruitful.
>>
>> If:
>>
>> a) it's considered that collections_jdk5 is ready, and
>> b) someone volunteers to be the release manager
>>
>> then I'll take a stab at the merge. Definitely done these
>> in the past,
>> though it's always fun when you can't walk over to the
>> people who made
>> the commits and get them to explain the problematic
>> change.
>>
>> First up would be to cp trunk to a 3.x branch. It's also
>> possible that
>> merging from trunk to the branch may prove easier.
>
> Damn it, Hen--that's part of the debate I wanted to save for a new thread!  ;)

I took a quick look. First up we should unify the license headers.
Change trunk to not have two spaces after the comment. That's causing
a lot of clashes. Once that's done I think it'll look nicer.

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message