I take this partially back. The gcj jvm is the one that doesn't work with ant. At any rate, going to a different JVM is something I can only influence but can't control, so that's probably not going to happen for a while.
Karl ________________________________________ From: Wright Karl (Nokia-S/Cambridge) Sent: Wednesday, June 09, 2010 5:24 AM To: connectors-dev@incubator.apache.org Subject: RE: Derby/JUnit bad interaction - any ideas? Open jdk does not seem to work properly with most java applications at this time, although it has continued to improve. Its switch incompatibilities stop it from working with ant at this time, so one cannot even build LCF with it. Karl ________________________________________ From: ext Olivier Bourgeat [olivier.bourg...@polyspot.com] Sent: Wednesday, June 09, 2010 4:03 AM To: connectors-dev@incubator.apache.org Subject: RE: Derby/JUnit bad interaction - any ideas? Debian Lenny have openjdk-6: http://packages.debian.org/fr/source/lenny/openjdk-6 Olivier Le mardi 08 juin 2010 à 22:37 +0200, karl.wri...@nokia.com a écrit : > MetaCarta is running Debian Lenny, which does not have a 1.6 version of Java > available at this time. > > Karl > > > -----Original Message----- > From: ext Jack Krupansky [mailto:jack.krupan...@lucidimagination.com] > Sent: Tuesday, June 08, 2010 4:36 PM > To: connectors-dev@incubator.apache.org > Subject: Re: Derby/JUnit bad interaction - any ideas? > > 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 > > > > > > > >
