[
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-02-aa-fixJarProperties.diff
Attaching derby-3988-02-aa-fixJarProperties.diff. This uncomments the JDBC4
data sources in the list of extra classes which need to be pulled in when we
build the jars. When the jdk16 property was deprecated, these classes were no
longer pulled into derby.jar. Touches the following file:
M tools/jar/extraDBMSclasses.properties
> 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,
> derby-3988-01-ad-alwaysCompileJDBC4.diff,
> derby-3988-02-aa-fixJarProperties.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.
