[
https://issues.apache.org/jira/browse/DERBY-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535863
]
Knut Anders Hatlen commented on DERBY-3117:
-------------------------------------------
I don't think we should disallow building Derby with newer JDKs. I like the
flexibility we get from saying that we require the ant process to use JDK 5 or
higher, since that means I know that if I use the most recent JDK as system
default and have ant.properties correctly set up, it'll just work when I type
'ant'. If we require exact version, that means I need to write scripts to
change the environment when I move between different projects.
Let me suggest a slightly different approach. What about changing the check in
the build script so that it uses java15compile.classpath and tries to compile a
file which uses JDK 6 features? Then we would detect if someone had mistakenly
set the compile classpath to Java 6. Is that foolproof enough? :)
> 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: 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_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.
