[
https://issues.apache.org/jira/browse/DERBY-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538525
]
Knut Anders Hatlen commented on DERBY-3117:
-------------------------------------------
Rick, do we need to check vendor? If people want such fine-grained control,
they could use ant.properties instead. For people who only want to compile
Derby, using the first JDK/SDK we find would probably suffice. Note that
setting compile.classpath does not change which compiler we use, only which
libraries the compiler uses to check that the methods/classes we use exist. So
the compiled byte code will look identical regardless of which vendor's class
library we use. The compiler only changes when we change JAVA_HOME.
> 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.
