[
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-ad-alwaysCompileJDBC4.diff
Attaching derby-3988-01-ad-alwaysCompileJDBC4.diff. This is identical to the
previous patch except that it adds a check to PropertySetter. The check aborts
the build if the IBM Java 5 compiler is being used and java16compile.classpath
is set. In that case, the build aborts, telling the user to either use a Java 6
compiler or unset java16compile.classpath.
Myrna, please let me know if this is an acceptable solution. I think that you
should be able to use the same ant.properties for your 10.5 and 10.4 builds as
long as you use a Java 6 compiler for both.
Thanks.
> 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
>
>
> 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.
