--- On Wed, 5/6/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: Wednesday, May 6, 2009, 6:22 AM
> On 06/05/2009, Matt Benson <gudnabr...@yahoo.com>
> wrote:
> >
> >
> >
> > --- On Tue, 5/5/09, sebb <seb...@gmail.com>
> wrote:
[SNIP]
> > > 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> ?
>
We have the option to enforce String keys if we want to break BC. Currently
the class uses String.valueOf(key) to accept other types. Personally I can't
see myself ever using this class so I really don't care. ;) I won't worry
about having offended the original authors with such a statement because it
appears (judging from order of @author tags) that they are all guys who have
long since moved on from Commons (Java?).
> There are also internal fields which can be made type
> safe.
> Every little helps.
>
When I went through the [collections] code I actually started working on this
class but got too many changes at once whirling around--brain started to bleed,
and I reverted lest I lose my mind completely. :D
> >
> > > 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 ;-)
>
Sure!
-Matt
> >
> > -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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
