[
https://issues.apache.org/jira/browse/DERBY-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538522
]
Rick Hillegas commented on DERBY-3117:
--------------------------------------
Hi Knut,
I think I understand what you're suggesting. We could eliminate the OS check
and just apply a bunch of heuristics to find the JDK directory regardless of
the underlying OS. After we find a directory, however, I think we still need to
switch based on JDK vendor. That is because the top-level JDK directory name
might be the same for two different vendors, but each vendor would still have
its own idea of what jars should be wired into java14compile.classpath and
java15compile.classpath.
> Adjust master build script to require the Java 5 compiler to build Derby
> ------------------------------------------------------------------------
>
> Key: DERBY-3117
> URL: https://issues.apache.org/jira/browse/DERBY-3117
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.4.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: BuildDefaults.txt, derby-3117-01-enforceJava5-aa.diff,
> derby-3117-01-enforceJava5-ab.diff, derby-3117-01-enforceJava5-ac.diff,
> derby-3117-02-website-aa.diff, derby-3117-03-junit-aa.diff, derby_source.html
>
>
> Require the Java 5 compiler in order to build Derby as approved by the
> community recently:
> http://www.nabble.com/-VOTE--Require-Java-5-%28or-later%29-compiler-to-build-Derby-tf4522491.html#a13030783
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
