[
https://issues.apache.org/jira/browse/DERBY-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657908#action_12657908
]
Rick Hillegas commented on DERBY-3988:
--------------------------------------
Thanks for the additional information, Myrna. I have reproduced your original
results on Ubuntu Linux. I ran the following experiments:
1) My environment has Sun and IBM JDKs for both Java 5 and Java 6
2) I built Derby with each of those four compilers. For each compiler, I ran
the build twice: first with no setting for java16compile.classpath, then later
with java16compile.classpath set to the Java 6 libraries supplied by the
compiler's vendor. So a total of eight builds:
i) Sun Java 5 compiler, java16compile.classpath NOT initially set
ii) Sun Java 5 compiler, java16compile.classpath initially set to Sun Java 6
libraries
iii) Sun Java 6 compiler, java16compile.classpath NOT initially set
iv) Sun Java 6 compiler, java16compile.classpath initially set to Sun Java 6
libraries
v) IBM Java 5 compiler, java16compile.classpath NOT initially set
vi) IBM Java 5 compiler, java16compile.classpath initially set to IBM Java 6
libraries
vii) IBM Java 6 compiler, java16compile.classpath NOT initially set
viii) IBM Java 6 compiler, java16compile.classpath initially set to IBM Java 6
libraries
All of the builds succeeded except for (vi), That build died with a "class file
has wrong version 50.0, should be 49.0" error when compiling java.sql.Blob, as
you discovered.
> 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.
