Jochen Wiedmann wrote:
> Besides, do not forget, that your patches should include Unit tests
> for the added features and that these Unit tests should work on
> 1.2-1.5 (by again detecting, whether java.util.concurrent is in
> place).
I didn't realize the next version ("3.0") was supposed to run on <1.4, or
even 1.2+ - my misunderstanding. I really don't have enough time to write
some commons-concurrent wrapper, let alone test it on a pre-1.5 VM. I will
take a look at the WorkerFactory however; maybe we can then use the
current implementation as fallback or a backport-util-concurrent /
1.5-util.concurrent factory depending on the VM we run on. However this is
not going to give any benefits in terms of locks or concurrent data
structures in the est of the code so I'm not sure if it's worth the
trouble. We'll see - thanks for the suggestions.
Holger
