Re: Master branch compile error using 1.5 spec.

Jeremy,

I think you actually need to use a 1.5 jvm to get this to compile. I have a machine that does this and there is one error which is easily fixable. ResultSet.isClosed does not exist in 1.5

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca

On Wed, Jan 22, 2014 at 6:04 AM, Jeremy Whiting <jwhiting@redhat.com> wrote:

Hi,
 Just to report I am getting a compile error on master branch. Using
this combination of command line arguments.

$ ant -Djava.specification.version=1.5 clean compile
....
[javac] 18 errors
[javac] 1 warning

 The full list of compilation errors are in the attached file.

 Shall I create an issue on GitHub to track this ?

Regards,
Jeremy


$ java -version
java version "1.7.0_51"
OpenJDK Runtime Environment (fedora-2.4.4.0.fc19-x86_64 u51-b02)
OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode)
$ ant -version
Apache Ant(TM) version 1.9.2 compiled on July 8 2013
$ uname -a
Linux f19lite 3.12.8-200.fc19.x86_64 #1 SMP Thu Jan 16 04:18:11 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux


--
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc

Surely no one should still be using JDK1.5 now!  Especially as JDK1.8 is due to be released in mid March and will be very much more secure than any previous release.  I suspect that people still using JDK1.5 are at risk from security problems fixed in JDK1.6 & JDK1.7.

I think that people still using JDK1.5 (including a client of mine) should be strongly encouraged to upgrade!


Cheers,
Gavin