commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <GGreg...@seagullsoftware.com>
Subject RE: [lang] 3.0, what's in; what's out
Date Sat, 14 Mar 2009 19:38:02 GMT
> -----Original Message-----
> From: sebb [mailto:sebbaz@gmail.com]
> Sent: Saturday, March 14, 2009 4:52 AM
> To: Commons Developers List
> Subject: Re: [lang] 3.0, what's in; what's out
> 
> On 14/03/2009, Henri Yandell <flamefew@gmail.com> wrote:
> > Starting up a thread for cleanup discussions on Lang.
> >
> >  I've removed the enum (was a blocker on JDK 5) and enums (people need
> >  to use real enums now) packages from Lang's trunk and moved them to a
> >  lang-backcompat sibling component. I've not made it a branch, it lives
> >  at the same level as trunk and will need its future to be decided.
> >
> >  An EnumUtils class has been added to the main lang package.
> >
> >  I also think the exception package should go. Again - the JDK has
> >  support for this now and there's no strong value in Lang having an
> >  alternative to stop people thinking about JDK 1.5. The ExceptionUtils
> >  class should move up to the main lang package and needs to have the
> >  Nestable Lang code removed from it. Presumably it still has value.
> >
> >  Some of the Date code is tempting to delete. Either due to buginess,
> >  or general 'this isn't that cool' ness.
> >
> >  JVMRandom should go. I'm not convinced it's had much use.
> >
> >  IDKey should move to package scoping - I've not seen an argument made
> >  yet for it being public.
> >
> >  Fraction is up for debate. Do we cede this to Commons Math. Sure it
> >  might add another jar to some people's code, but probably good for
> >  them to be more aware of Math.
> >
> >  WordUtils and StringEscapeUtils both strike me as 'desirable but
> >  flawed'. We should consider overhauls.
> >
> >  The Security requiring stuff in builder for reflection needs to go
> >  away imo. Makes it less than useful.
> >
> >  We need a PackageUtils in reflect.
> >
> >  We need to consider if there are any annotations that are valuable to
> >  be pseudo-standard.
> >
> >  I'm still partial to a RegexUtils.
> >
> >  Plus general generifying, varargs, autoboxing.
> >
> >  Deletion of all deprecated methods/classes.
> >
> >  And the various other backwards incompatible changes that people have
> >  been requesting.
> 
> Removal of AllxxxTest classes that just group other tests.
> These just tend to get out of date, potentially complicate the POM,
> and IMO don't offer much added value.

-1

I use package-level test suites all the time from Eclipse. Running all tests in a given package
is a very reasonable thing to do IMO. Otherwise I am forced to the command line where I often
cannot ask Ant or Maven to even run tests in a given package. I am stuck with whatever the
build's test target does. Not only that but I'd have to sit through a build every time...

> 
> Documentation of thread safety, make variables final where possible.
> Add @Immutable, @GuardedBy etc JCIP annotations.
> 
> Prefer values set via constructor rather than set() methods.
> 
> Make all mutable variables private.
> Ensure constructors don't call non-final non-private methods.
> 
> >  Hen
> >
> >  ---------------------------------------------------------------------
> >  To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >  For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org


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


Mime
View raw message