On 26/08/13 18:21, Rob Vesse wrote:
Yeah we use JDK6 exclusively here at YarcData
The fix is either to make the change or I think we can use the compiler
plugin to restrict these modules to JDK 6 for the time being?
Rob
I'd prefer the change if it has no effect on Java6 - I'm not sure what's
going to happen to the signatures of the abstract class between java6
and java7 runtimes. Presumably that works otherwise there would be lots
fo focums/stackoverflow items.
Does it get in the way in Java6?
Andy
On 8/26/13 3:04 AM, "Andy Seaborne" <[email protected]> wrote:
I'm getting the following compile time error when building with maven.
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
(default-compile) on project jena-jdbc-core: Compilation failure:
Compilation failure:
[ERROR]
/home/afs/Jena/jena-jdbc/jena-jdbc-core/src/main/java/org/apache/jena/jdbc
/metadata/results/MetaResultSet.java:[51,8]
org.apache.jena.jdbc.metadata.results.MetaResultSet is not abstract and
does not override abstract method
<T>getObject(java.lang.String,java.lang.Class<T>) in java.sql.ResultSet
and then some others.
Maybe it's this:
http://stackoverflow.com/questions/7692320/is-there-really-resultset-getob
jectstring-classt-in-jdk7
I'm using a Java7 compiler in Java6 mode so it's the JDK7 runtime.
If so, the fix is to add, without @Override but with suppressed warnings:
<T> T getObject(int columnIndex, Class<T> type) throws SQLException
<T> T getObject(String columnLabel, Class<T> type) throws SQLException
Andy
