You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <de...@db.apache.org> on 2006/03/07 00:50:32 UTC
[jira] Created: (DERBY-1078) Be able to build Derby when JAVA_HOME
is set 1.6
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
Versions: 10.2.0.0
Reporter: Rick Hillegas
Fix For: 10.3.0.0
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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Dyre Tjeldvoll (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12375328 ]
Dyre Tjeldvoll commented on DERBY-1078:
---------------------------------------
Please ignore the last comment, it was intended for another issue.
> 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
>
> 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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12375225 ]
Andrew McIntyre commented on DERBY-1078:
----------------------------------------
Sanity check on j9, jdk13, and jdk142 look good. Committed derby-1078.diff to trunk with revision 395458. Rick, please resolve and/or close if this takes care of this issue.
> 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
>
> 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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12369284 ]
Dag H. Wanvik commented on DERBY-1078:
--------------------------------------
> 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 option seems to do it:
javac --help:
:
-target <release> Generate class files for specific VM version
> 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
>
> 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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12375458 ]
Andrew McIntyre commented on DERBY-1078:
----------------------------------------
Committed another patch with revision 395749 to get client and demo working with 1.3 when compiled with 1.5 or higher. Unlike the engine, 1.3- and 1.4-dependent code are not well separated. So, fixed by asking the compiler to generate 1.3-compatible classes, but linked against the 1.4 runtime classes. Client now passes the jdbcapi suite. Also fixed demo just by switching entirely over to 1.3. It was not dependent on any 1.4-specific methods.
This just leaves scouring the java/testing hierarchy for the remaining classes which should be built as 1.3, but are currently compiled by a 1.4 dependent target. This is quite a few tests, but they are easily identifiable because they error out immediately with UnsupportedClassVersionError.
> 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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12377609 ]
Rick Hillegas commented on DERBY-1078:
--------------------------------------
Hi Andrew,
You can use the ant <replace> task for this. Thanks for digging into this problem!
> 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
>
> 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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Knut Anders Hatlen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12375886 ]
Knut Anders Hatlen commented on DERBY-1078:
-------------------------------------------
The storerecovery tests have failed a couple of days because the files in java/testing/org/apache/derbyTesting/functionTests/util/corruptio/ are no longer compiled. Added the missing files to functionTests/util/build.xml and committed revision 396285.
> 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
[jira] Updated: (DERBY-1078) Be able to build Derby when JAVA_HOME
is set 1.6
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=all ]
Andrew McIntyre updated DERBY-1078:
-----------------------------------
Attachment: derby-1078_part3.diff
Attaching patch3 to resolve the problem with the parsers in IBM JDK 1.3.1 mentioned above. I will commit this shortly if there are no objections.
> 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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Dyre Tjeldvoll (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12375322 ]
Dyre Tjeldvoll commented on DERBY-1078:
---------------------------------------
Since revision 395458 I can no longer run jdbcapi/metadata.java with DerbyNetClient under java 1.3. (Still compiling with 1.4). I get the following error:
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/apache/derby/iapi/services/i18n/MessageService (Unsupported major.minor version 48.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:488)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:106)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:243)
at java.net.URLClassLoader.access$100(URLClassLoader.java:51)
at java.net.URLClassLoader$1.run(URLClassLoader.java:190)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:183)
at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:288)
at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:310)
at org.apache.derby.impl.tools.sysinfo.Main.getCompleteMessage(Main.java:1077)
at org.apache.derby.impl.tools.sysinfo.Main.getTextMessage(Main.java:1056)
at org.apache.derby.impl.tools.sysinfo.Main.<clinit>(Main.java:316)
at org.apache.derby.tools.sysinfo.main(sysinfo.java:52)
Framework: DerbyNetClient
*** Start: metadata jdk1.3.1_15 DerbyNetClient 2006-04-20 11:17:30 ***
> 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
>
> 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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12370759 ]
Rick Hillegas commented on DERBY-1078:
--------------------------------------
Bryan adds:
Can you use <presetdef> for this? It lets you override/extend tasks and provide additional parms, etc.
http://ant.apache.org/manual/CoreTasks/presetdef.html
http://stefan.samaflost.de/blog/en/Apache/Ant/customization_and_user_preferences_with_presetdef.writeback
> 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
>
> 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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ 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 ***
1a2
> 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: 10.2.0.0
> Reporter: Rick Hillegas
> Fix For: 10.2.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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12377601 ]
Andrew McIntyre commented on DERBY-1078:
----------------------------------------
If I qualify the inherit references to tokenImage in both ij.java and SQLParser.java by adding their classnames (e.g. in ij.java, tokenImage --> ijConstants.tokenImage, and in SQLParser.java, tokenImage --> SQLParserConstants.tokenImage) then the tests pass. So, as a workaround I'd like to sed the classname into the generated file at build time.
This clearly appears to be a JVM issue with IBM JDK 1.3.1, but if there are no objections, I'd like to put in this workaround until support for JDK 1.3.1 is removed.
> 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
>
> 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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12377645 ]
Andrew McIntyre commented on DERBY-1078:
----------------------------------------
Committed patch3 with revision 399450.
> 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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12376534 ]
Andrew McIntyre commented on DERBY-1078:
----------------------------------------
Committed revision 397278. Fixes XA, encryption and a couple of other tests on 1.3.1. I'm still seeing some diffs in store tests, but they don't look related to this issue, they look like a timing/harness issue, might just be on my machine. I'll double check on another platform and follow up later.
> 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.2.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
Re: [jira] Commented: (DERBY-1078) Be able to build Derby when JAVA_HOME is set 1.6
Posted by Andrew McIntyre <mc...@gmail.com>.
On 3/7/06, Bryan Pendleton <bp...@amberpoint.com> wrote:
> Andrew McIntyre wrote:
> > Well, unless
> > it actually lets you redefine <javac>...
>
> I believe it does, though Ant will then give you a warning message.
It seems like this might break, or at least lead to unexpected results
on occasion, when building at the leaf level, if the <presetdef> is
only in the top-level file. You could put the <presetdef> in every
build.xml, but then why not just add target="1.4" to all the <javac>s?
Don't know how I feel about that, I'd have to play around with it to
see how it actually works.
Thanks for pointing out <presetdef> though, good to know.
andrew
Re: [jira] Commented: (DERBY-1078) Be able to build Derby when JAVA_HOME
is set 1.6
Posted by Bryan Pendleton <bp...@amberpoint.com>.
Andrew McIntyre wrote:
> Well, unless
> it actually lets you redefine <javac>...
I believe it does, though Ant will then give you a warning message.
bryan
Re: [jira] Commented: (DERBY-1078) Be able to build Derby when JAVA_HOME is set 1.6
Posted by Andrew McIntyre <mc...@gmail.com>.
On 3/7/06, Bryan Pendleton <bp...@amberpoint.com> wrote:
>
> Can you use <presetdef> for this? It lets you override/extend tasks and provide additional parms, etc.
>
> http://ant.apache.org/manual/CoreTasks/presetdef.html
> http://stefan.samaflost.de/blog/en/Apache/Ant/customization_and_user_preferences_with_presetdef.writeback
Nice! That looks like the templated task feature I was referring to. I
missed that it was added in 1.6.
But, looking at how they implemented it, it doesn't necessarily make
this any easier. You'll still need to update all the build.xml files
to use the new presetdef task instead of vanilla <javac>. Well, unless
it actually lets you redefine <javac>...
andrew
Re: [jira] Commented: (DERBY-1078) Be able to build Derby when JAVA_HOME
is set 1.6
Posted by Bryan Pendleton <bp...@amberpoint.com>.
Andrew McIntyre (JIRA) wrote:
> unfortunately you'll need to update all of the <javac> tasks in the build.xml to include target="1.4"
Can you use <presetdef> for this? It lets you override/extend tasks and provide additional parms, etc.
http://ant.apache.org/manual/CoreTasks/presetdef.html
http://stefan.samaflost.de/blog/en/Apache/Ant/customization_and_user_preferences_with_presetdef.writeback
bryan
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12369285 ]
Andrew McIntyre commented on DERBY-1078:
----------------------------------------
I don't think Ant has templated tasks yet, it's been a long-requested feature, but I don't think it's been added yet. So, this is possible, but unfortunately you'll need to update all of the <javac> tasks in the build.xml to include target="1.4" with the exception, of course, of the new files for 1.6. Should be doable with a pretty simple Perl script.
> 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
>
> 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
[jira] Closed: (DERBY-1078) Be able to build Derby when JAVA_HOME
is set 1.6
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=all ]
Rick Hillegas closed DERBY-1078:
--------------------------------
> 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.2.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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12375185 ]
Rick Hillegas commented on DERBY-1078:
--------------------------------------
Beautiful. It's a lot of edits but they have a familiar rhythm to them. Thanks for all this work! After applying the patch, I successfully built under 1.4, 1.5, and 1.6. After each build, I successfully ran the grantRevoke test under 1.4 and the jdbc40 suite under 1.6.
> 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
>
> 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
[jira] Closed: (DERBY-1078) Be able to build Derby when JAVA_HOME
is set 1.6
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=all ]
Rick Hillegas closed DERBY-1078:
--------------------------------
> 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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12377524 ]
Andrew McIntyre commented on DERBY-1078:
----------------------------------------
Committed revision 399164. This fixes a couple more tests under jdk131, specifically stress.multi and dataSourcePermissions related tests. This should finally return the jdk131 tests to the state prior to any DERBY-1078 changes. See:
http://people.apache.org/~fuzzylogic/derby_test_results/main/testlog/jdk131/392471-derbyall_diff.txt
The testSecMec problem is specific to the test, and it appears we should not run SqlExceptionTest.junit under jdk131 due to its use of the jdk14-specific initCause() method. I believe the DerbyNetAutoStart.java test to be instability in the test. See DERBY-803.
BUT, testing with IBM JDK 1.3.1 is showing a huge amount of failures due to a problem with the ij parser. The problem manifests itself as follows:
*** Start: big jdk1.3.1 DerbyNet derbynetmats:derbynetmats 2006-04-30 01:04:17 ***
4 del
< 0 rows inserted/updated/deleted
4a4
JAVA ERROR: java.lang.NoSuchFieldError: org.apache.derby.tools.ij.ij: field tokenImage not found
tokenImage is a String array in the interface ijConstants, which ij.java implements. So, the ij parser should be able to access the array by virtue of inheritence. It's not clear why the IBM jdk can't find the tokenImage array in ijConstants. I'm searching for a resolution to the problem, but if I cannot find one, I may have to back all of these changes out after we branch 10.2.
> 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
>
> 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
[jira] Reopened: (DERBY-1078) Be able to build Derby when JAVA_HOME
is set 1.6
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=all ]
Andrew McIntyre reopened DERBY-1078:
------------------------------------
Assign To: Andrew McIntyre
Reopening this issue due to ij,jj issue with IBM JDK 1.3.1. See following comment.
> 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
>
> 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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Dyre Tjeldvoll (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12375327 ]
Dyre Tjeldvoll commented on DERBY-1078:
---------------------------------------
I have looked at the new patch and I think it looks good. Even better than the first which was also good ... :) IMHO, it is ready to be committed.
> 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
>
> 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
[jira] Updated: (DERBY-1078) Be able to build Derby when JAVA_HOME
is set 1.6
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-1078) Be able to build Derby when JAVA_HOME
is set 1.6
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=all ]
Andrew McIntyre updated DERBY-1078:
-----------------------------------
Attachment: derby-1078.diff
Attached patch adds appropriate source and target attributes to all javac tasks in the build. I want to do a number of tests before submitting this, primarily running a Derby built with a newer build on jdk131 and j9 (=JSR169). But, with this patch, you can now run a full build with Ant running in JDK 1.5 (and thus, with JDK 1.5's compiler).
> 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
>
> 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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12375226 ]
Andrew McIntyre commented on DERBY-1078:
----------------------------------------
Sanity check on j9, jdk13, and jdk142 look good. Committed derby-1078.diff to trunk with revision 395458. Rick, please resolve and/or close if this takes care of this issue.
> 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
>
> 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
[jira] Resolved: (DERBY-1078) Be able to build Derby when JAVA_HOME
is set 1.6
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=all ]
Rick Hillegas resolved DERBY-1078:
----------------------------------
Fix Version: 10.2.0.0
(was: 10.3.0.0)
Resolution: Fixed
> 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.2.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
[jira] Resolved: (DERBY-1078) Be able to build Derby when JAVA_HOME
is set 1.6
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-1078) Be able to build Derby when JAVA_HOME
is set 1.6
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=all ]
Rick Hillegas updated DERBY-1078:
---------------------------------
Component: Build tools
> 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
>
> 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
[jira] Commented: (DERBY-1078) Be able to build Derby when
JAVA_HOME is set 1.6
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12375656 ]
Andrew McIntyre commented on DERBY-1078:
----------------------------------------
Committed revision 396035 which fixes the remaining issues in the tests built with JDK 1.5 or higher and then run on JDK 1.3.
> 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