[
https://issues.apache.org/jira/browse/DERBY-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657913#action_12657913
]
Rick Hillegas commented on DERBY-3988:
--------------------------------------
Hi Myrna,
I also want to follow up on another comment you made:
> Re building Driver40 with my sun setup; I maybe should have mentioned that
> when I build with the sun jvms, there is no need for the
> java*compile.classpath settings...
This says to me that the PropertySetter program is correctly finding your Sun
JDKs. That's good. Has the build been failing for you when you use an IBM
compiler but don't set the java*compile.classpath variables? That would be bad.
That suggests to me that PropertySetter isn't smart enough to find your IBM
JDKs. We may be able to fix PropertySetter so that it finds the IBM JDKs on
your machine.
Thanks,
-Rick
> 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
>
>
> 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.
