[
https://issues.apache.org/jira/browse/DERBY-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535952
]
Rick Hillegas commented on DERBY-3117:
--------------------------------------
I agree that we could add that check to the compiler verification target which
is invoked during build initialization. It would reduce the brittleness, but
probably not eliminate it. We could imagine adding similar checks to make sure
that the jdk14 and jsr169 classpaths are sensible too. However, I don't have
confidence that this approach will prove the correctness of the code at
compile-time. Getting people to declare these variables up front , as you
suggest, probably mops up most of the problems. The remaining problems can be
flushed out after checkin when the build breaks on someone else's machine--I
think that risk is acceptably small. Thanks.
> 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.
