[ http://issues.apache.org/jira/browse/DERBY-1078?page=all ]
Andrew McIntyre resolved DERBY-1078:
------------------------------------
Resolution: Fixed
Marking this resolved. JDK 1.3.1 tests show several problems, but none related
to this issue:
http://people.apache.org/~fuzzylogic/derby_test_results/main/testSummary-405977.html
> 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
> Assignee: Andrew McIntyre
> Fix For: 10.2.0.0
> Attachments: derby-1078.diff, derby-1078_part2.diff, derby-1078_part3.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
