On 06/05/2009, Matt Benson <gudnabr...@yahoo.com> wrote: > > > > --- On Tue, 5/5/09, sebb <seb...@gmail.com> wrote: > > > From: sebb <seb...@gmail.com> > > > Subject: Re: [COLLECTIONS] 3.3 release > > To: "Commons Developers List" <dev@commons.apache.org> > > > Date: Tuesday, May 5, 2009, 6:02 PM > > > On 05/05/2009, Matt Benson <gudnabr...@yahoo.com> > > wrote: > > > > > > > > > > > > --- On Thu, 4/30/09, James Carman <ja...@carmanconsulting.com> > > wrote: > > > > > > > From: James Carman <ja...@carmanconsulting.com> > > > > Subject: Re: [COLLECTIONS] 3.3 release > > > > To: "Commons Developers List" <dev@commons.apache.org> > > > > Date: Thursday, April 30, 2009, 12:18 AM > > > > > > > I would love to see a collections > > > > version that is based on > > > > commons-functor (once it's generified). > > > > > > > > > Notwithstanding the fact that I'm way behind on email, > > what is "it" above? > > > > > > [functor]'s generification has been complete for > > nearly a year. > > > [collections] is done in the branch AFAIK. > > I simply haven't had time to figure out how to get svn to > > merge it back to trunk. > > > > > > > If you are referring to the branch > > "collections_jdk5_branch" then > > ExtendedProperties still needs to be genericised. > > > > > This class can't be made generic in a meaningful way, IMO. We can make the > gesture and say it extends Hashtable<Object, Object> FWIW.
[which is what java.util.Properties does] Or Hashtable<String, Object> ? There are also internal fields which can be made type safe. Every little helps. > > > There are over 1000 missing @Override markers (some in test > > classes) > > and a few missing @Deprecated markers. > > > Okay, but give me a break. Those aren't "real" work... :) Huh? each one should really be checked to ensure that the override is intentional ;-) > > -Matt > > > > > > > -Matt > > > > > > > > > > > > > > On Thu, Apr 30, 2009 at 1:14 AM, Henri > > Yandell <flame...@gmail.com> > > > > wrote: > > > > > 3.3 is a whole load of bugfixes that > > have accumulated. > > > > I added a few > > > > > more likely tickets. > > > > > > > > > > I've been paying more attention to > > Jakarta Taglibs and > > > > trying to get > > > > > JSTL out there than Collections (which > > is a bit of an > > > > indictment on my > > > > > mental state as that's meant > > mavenizing that project > > > > rather than > > > > > working out Collections' situation). > > > > > > > > > > I'm not sure if Collections is > > releasable from Maven2 > > > > - that's the > > > > > next step for 3.3 to figure out if > > anything needs to > > > > change to make it > > > > > more akin to the others. > > > > > > > > > > Hen > > > > > > > > > > On Tue, Apr 28, 2009 at 2:27 PM, Gary > > Gregory > > > > > <ggreg...@seagullsoftware.com> > > > > wrote: > > > > >> I think adding generics would be > > great. Even if > > > > the next version only adds generics, that > > is reason enough > > > > for me to help and upgrade our apps. > > Release early, release > > > > often. > > > > >> > > > > >> Gary > > > > >> > > > > >>> -----Original Message----- > > > > >>> From: Dave Meikle [mailto:loo...@gmail.com] > > > > >>> Sent: Tuesday, April 28, 2009 > > 11:09 AM > > > > >>> To: dev@commons.apache.org > > > > >>> Subject: [COLLECTIONS] 3.3 > > release > > > > >>> > > > > >>> Hi, > > > > >>> > > > > >>> I know late last year Henri > > spoke about doing > > > > a 3.3 release of Collections > > > > >>> but I assume other commitments > > took over - > > > > this certainly keeps happening > > > > >>> to > > > > >>> me just now. > > > > >>> > > > > >>> I see there are some new > > tickets that need > > > > some minor work, so was > > > > >>> wondering > > > > >>> what are the current plans? > > > > >>> > > > > >>> Apologises if I have missed a > > previous posting > > > > on this. > > > > >>> > > > > >>> Cheers, > > > > >>> Dave > > > > >> > > > > >> > > > > > > --------------------------------------------------------------------- > > > > > >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > >> For additional commands, e-mail: > > dev-h...@commons.apache.org > > > > >> > > > > >> > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
