directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel L├ęcharny <>
Subject Re: Concurrent classes in junit-addons
Date Tue, 08 Feb 2011 23:26:24 GMT
On 2/9/11 12:18 AM, Stefan Seelmann wrote:
>> All in all, switching to Java 6 is not *that* bad. i'm just wondering if the
>> problem we have with the concurrent test tooling (which requires Java6)
>> can't be workarounded by requiring the code to be compiled using Java 5 and
>> run with Java 6.
>> If not, then, well, let's go for Java 6
> I think a test dependency (even when helpful by speeding up the build
> and detecting concurrency issues) isn't worth that step.
> I agree with Emmanuel that Java 5 or older is still used in companies
> (just like in my current project). But I think Java 5 is mainly used
> by commercial software like the fat application servers or ERP
> software. If a company decides to use ApacheDS we can expect that they
> know that there is something beyond Java 5.
I was more specifically thinking about companies using ADS for unit 
tests. I have some clients doing that.

Emmanuel L├ęcharny

View raw message