[
https://issues.apache.org/jira/browse/DERBY-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-3988:
---------------------------------
Attachment: derby-3988-01-ab-alwaysCompileJDBC4.diff
Attaching derby-3988-01-ab-alwaysCompileJDBC4.diff. This patch makes the 3
improvements suggested by Knut:
1) Doesn't fork while compiling the JDBC4 support
2) Compiles the JDBC4 support to Java 6 byte code if possible
3) Removes the "optional" prefixes on the JDBC4 modules in modules.properties
Touches the following files:
M java/engine/org/apache/derby/impl/jdbc/build.xml
M java/engine/org/apache/derby/iapi/jdbc/build.xml
M java/engine/org/apache/derby/jdbc/build.xml
M java/engine/org/apache/derby/modules.properties
M java/engine/build.xml
M java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/build.xml
M java/client/build.xml
M build.xml
> 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
>
>
> 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.
