[
https://issues.apache.org/jira/browse/DERBY-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662979#action_12662979
]
Knut Anders Hatlen commented on DERBY-3988:
-------------------------------------------
The fixJarProperties patch looks good to me. By the way, the jdk16 property is
still used in build.xml (for building javadoc and running JUnit tests) even
though it's been removed from the build instructions.
Should the same change also be made to tools/jar/dnc.properties?
Could we now remove this target from build.xml?
<target name="jdbc4_classlist_edit" if="jdk16">
<!-- uncomment jdbc4 classes if jdk 1.6 is available -->
<echo level="info" message="uncommenting jdbc4 classes"/>
<replaceregexp file="${jar.classlist}"
match="^#jdbc4_optional_(.*)"
replace="\1"
byline="true"/>
</target>
> 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.
