Army wrote:
I was trying to run some sanity checks as part of my work for
DERBY-1758 and I noticed that the new JUnit test I created hangs when
I run with ibm131 and jdk131.
My new test uses "TestConfiguration.defaultSuite()", which means the
test will run against embedded first and then against the Derby
Client. The embedded tests all complete without problem, but a hang
occurs while preparing for the client tests.
I think the underlying issue is DERBY-300, which is specific to 1.3
JVMs. And since we're saying that the 1.3 JVMs are deprecated as of
10.3, I guess the "solution" could just be to avoid running JUnit
tests on 1.3 JVMs.
Hi Army,
My understanding is that once Java SE 6 goes GA, 1.3 will become an
unsupported platform. See the end-of-life disclaimer at the top of
http://java.sun.com/j2se/1.3/download.html. When we polled the user
community last year, no-one said that they were using 1.3. The developer
community voted to stop supporting 1.3 in the 10.3 release. After Java
SE 6 goes GA, I think we should amend the Derby build to swap out 1.3
and swap in Java SE 6.
I agree with your solution. I don't see any reason to spend time on a
configuration which is about to be officially unsupported, which our
users don't care about, and which we have voted to deprecate. I don't
think that the 1.3 tests in the trunk are anybody's itch at this point.
Is that the correct conclusion, or is this something worth addressing,
presumably in the JUnit setup code somewhere?
Army
- Re: JUnit "TestConfiguration.defaultSuite()&quo... Rick Hillegas
-
