db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1078) Be able to build Derby when JAVA_HOME is set 1.6
Date Thu, 27 Apr 2006 04:45:05 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12376635 ] 

Andrew McIntyre commented on DERBY-1078:

I could not reproduce the diffs that I had seen in the store unit tests in a different environment,
so I guess this must have been something specific to that particular test environment. So,
I think that all potential issues surrounding these changes have been resolved.

For reference, in case someone sees them in another environment, here is the diff that was
present in each of the tests that had the problem:

*** Start: recoveryTest jdk1.3.1_16 storeall:storeunit 2006-04-23 10:42:14 ***
> WARNING: Derby (instance xxxxFILTERED-UUIDxxxx) is attempting to boot the data
base /Users/andrewm/derby/testdir/131/derbyall/storeall/storeunit/storeunit/Reco
veryTest even though Derby (instance xxxxFILTERED-UUIDxxxx) may still be active.
  Only one instance of Derby should boot a database at a time. Severe and non-re
coverable corruption can result and may have already occurred.
Test Failed.
*** End:   recoveryTest jdk1.3.1_16 storeall:storeunit 2006-04-23 10:42:34 ***

> 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:
>     Reporter: Rick Hillegas
>      Fix For:
>  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:
For more information on JIRA, see:

View raw message