On 10/28/07, Stephen Kestle <[EMAIL PROTECTED]> wrote:
> NB!!! Don't submit patches for CollectionUtils --- I have it 90%
> complete, and will find time to do the other 10% if people want to see
> it (are people actually using the generics branch? I am, but then I know
> it's as good as my own co
But can't the library be first moved to a point where one can say the
new releases will run only on 1.5+ JVM, and then
gradually/slowly/carefully re-work/generify the internals as necessary
? So at least this won't constrain any new development effort from
using all the goodies in 1.5+, and yet
The plan is for non backwards compatibility, as there are too many
things that don't make sense for generics, and some things that plain
don't work. The Map coercion methods become silly, and TransformedMap
can't conform to the map interface in it's current form (is that the
right one?).
Hav
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-jaxme has an issue affecting its community
integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-jsl-test has an issue affecting its community
integration.
Th
Sounds like a threading issue. I'd assume DescriptiveStatistics is
not thread-safe and in your stacktrace I see
at no.mypackage.spring.utils.ExecutionTimeAdviceTest$1.run
(ExecutionTimeAdviceTest.java:47)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run
(Unknown Source)
