[ http://issues.apache.org/jira/browse/DERBY-1078?page=all ]
Andrew McIntyre updated DERBY-1078:
-----------------------------------
Attachment: derby-1078_part2.diff
So it appears that my initial jdk131 test was misleading. Attaching a patch
that at least gets Derby to pass metadata.java, and committed with revision
395643.
I'll be running derbyall on jdk131 to clean up any lingering failures.
One note on the patch: I had to add xercesImpl and xml-apis to tools/java
because the compile of the XML datatype ended up pulling in most of iapi/types
and iapi/services as side-compiles.
> Be able to build Derby when JAVA_HOME is set 1.6
> ------------------------------------------------
>
> Key: DERBY-1078
> URL: http://issues.apache.org/jira/browse/DERBY-1078
> Project: Derby
> Type: Improvement
> Components: Build tools
> Versions: 10.2.0.0
> Reporter: Rick Hillegas
> Fix For: 10.3.0.0
> Attachments: derby-1078.diff, derby-1078_part2.diff
>
> Currently, the 1.4 compiler is used to build most of Derby. We use the 1.6
> compiler to (optionally) build the JDBC4 support. If you try to build Derby
> in a shell window with a 1.6 JAVA_HOME, the 1.4 bits will fail to build. This
> is because those bits do not satisfy the JDBC4 contract. In addition, even if
> you could build those bits under 1.6, the 1.6 class files would fail to load
> on a 1.4 vm.
> We need to be able to use 1.6 as our default build environment but still
> generate jar files which run on 1.4 and 1.5. There may be compiler switches
> which allow this. If not, building in a 1.6 environment could fault in the
> 1.4 compiler as necessary.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
