Separate out the small number of build targets which really require JDK1.4
features from the bulk of the targets which ought to compile cleanly against
small device libraries
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: DERBY-3984
URL: https://issues.apache.org/jira/browse/DERBY-3984
Project: Derby
Issue Type: Improvement
Components: Build tools
Affects Versions: 10.5.0.0
Reporter: Rick Hillegas
It would be good to make jsr169 the default platform for most Derby build
targets. This will allow the build to raise compile-time errors when a checkin
violates the small-device contract. Only a small number of features (listed in
DERBY-3966) really require JDK1.4. Something like the following may work:
1) Finish up DERBY-3966 so that java4compile.classpath defaults to an
approximation of ${jdk14xmlSupport}: ${java15compile.classpath}
2) Make compile.classpath default to jsr169compile.classpath
3) Fortunately, jsr169compile.classpath itself already defaults to
${jsr169stubs}:${java14compile.classpath}
4) Change a (hopefully) small number of targets to use java14compile.classpath
rather than compile.classpath
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.