If we need to require Java 1.6, that is probably okay. I am fine with that.
Does anybody have a serious objection to requiring Java 1.6 for LCF?
-- Jack Krupansky
--------------------------------------------------
From: <karl.wri...@nokia.com>
Sent: Tuesday, June 08, 2010 6:35 AM
To: <connectors-dev@incubator.apache.org>
Subject: Derby/JUnit bad interaction - any ideas?
I've been trying to get some basic tests working under Junit.
Unfortunately, I've run into a Derby problem which prevents these tests
from working.
What happens is this. Derby, when it creates a database, forces a number
of directories within the database to "read-only". Unfortunately, unless
we stipulate Java 1.6 or up, there is no native Java way to make these
directories become non-read-only. So database cleanup always fails to
actually remove the old database, and then new database creation
subsequently fails.
So there are two possibilities. First, we can change things so we never
actually try to clean up the Derby DB. Second, we can mandate the java
1.6 is used for LCF. That's all there really is.
The first possibility is tricky but doable - I think. The second would
probably be unacceptable in many ways.
Thoughts?
Karl
