[
https://issues.apache.org/jira/browse/DERBY-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656596#action_12656596
]
Knut Anders Hatlen commented on DERBY-3988:
-------------------------------------------
Bryan Pendleton <[email protected]> writes:
>> Is there any reason why we couldn't just take the full step and
>> require JDK 6 instead of JDK 5?
>
> To be clear, you propose to require JDK 6 for *building* Derby, but
> the code, once built, would continue to run in the current set of
> environments (JDK 1.4+, small environment, etc.)?
>
> If so, that approach seems fine to me.
Yes, that's what I meant. Require JDK 6 (or later) to build Derby, but
Derby should continue to run on the same platforms as before.
> 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
>
>
> 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.
