[
https://issues.apache.org/jira/browse/DERBY-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657166#action_12657166
]
Myrna van Lunteren commented on DERBY-3988:
-------------------------------------------
I didn't get a chance to test out the patch before your commit.
Now, when I build with sun jvms/jres all is fine, but when I build with ibm
jres, I get this:
compile_jdbc4:
[javac] Compiling 5 source files to C:\derbyt\svn\trunk\classes
[javac]
C:<myrnaspathto>trunk\java\engine\org\apache\derby\iapi\jdbc\BrokeredCallableStatement40.java:26:
cannot access java.sql.Blob
[javac] bad class file:
c:<myrnaspathtoibm16>\jre\lib\sql.jar(java/sql/Blob.class)
[javac] class file has wrong version 50.0, should be 49.0
[javac] Please remove or make sure it appears in the correct subdirectory
of the classpath.
[javac] import java.sql.Blob;
[javac] ^
[javac] 1 error
[javac] Compile failed; see the compiler error output for details.
> Set the Java 6 complilation path based on the Java 5 compilation path so that
> the JDBC4 support is always built
> ---------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3988
> URL: https://issues.apache.org/jira/browse/DERBY-3988
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.5.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-3988-01-aa-alwaysCompileJDBC4.diff,
> derby-3988-01-ab-alwaysCompileJDBC4.diff,
> derby-3988-01-ac-alwaysCompileJDBC4.diff
>
>
> Now that we have checked in the JDBC4 stubs, it ought to be possible to build
> the JDBC4 support with just the Java 5 libraries and compiler. Set
> java16compile.classpath=${jdbc4stubs}:${java15compile.classpath}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
