[
https://issues.apache.org/jira/browse/DERBY-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657022#action_12657022
]
Knut Anders Hatlen commented on DERBY-3988:
-------------------------------------------
> Are you planning to add references to new Java 6 classes/methods soon?
No.
> If so, do you have some other proposals in mind besides (1) and (2)?
You also have this option:
3) Build JDBC 4.0 only when using JDK 6 or later (though automatically, as you
suggested, without setting the jdk16 property)
Then JDBC 4.0 support will be built automatically for everyone who has
installed JDK 6, it won't break the build for those who are still using JDK 5,
and it doesn't prevent using the full power of JDK 6 in code that is written
for JDK 6. The downside is that the JDBC 4.0 driver is not compiled on
platforms where JDK 6 is not yet available.
But I'm fine with the latest proposal for now.
> 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.
