[
https://issues.apache.org/jira/browse/DERBY-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541835
]
Daniel John Debrunner commented on DERBY-3117:
----------------------------------------------
Is it possible to put this functionality in an optional target for now, that
would allow others to test it and add support for other vms before enabling it
as the default?
E.g. with a target of setprops one could do:
ant setprops all
> 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-3117-04-propertySetter-aa.diff, derby-3117-04-propertySetter-ab.diff,
> derby-3117-04-propertySetter-ac.diff, derby-3117-04-propertySetter-ad.diff,
> derby-3117-04-propertySetter-ae.diff, derby-3117-04-propertySetter-af.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.
