Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
10.12.1.1
-
None
Description
Derby can't be built with JDK 9. Java 9 introduces new JDBC classes like java.sql.ShardingKey and methods which refer to these new classes.
In addition, project Jigsaw has created a new way to name classes (see http://openjdk.java.net/jeps/220). This breaks the PropertySetter build tool which we use so that old JVMs can compile Derby and so that Derby can be compiled to run on old JVMs.
It is likely that we will need to leave this issue open throughout the development cycle of Java 9.
Attachments
Attachments
Issue Links
- incorporates
-
DERBY-6932 Migrate finalization to the new Cleaner-based pattern introduced by JDK 9 build 167
- Open
- is related to
-
DERBY-6998 Make it possible to build Derby cleanly using JDK 10
- Open
-
DERBY-6465 Add JDK 9 to the list of JVMs which can be used to build and test Derby
- Open
-
DERBY-6945 Re-package Derby as a collection of jigsaw modules
- Closed
-
DERBY-6974 Deprecate support for building Derby under JDK 8
- Open
- relates to
-
DERBY-4762 Failure in testPing
- Closed
-
DERBY-6857 Deprecate support for building Derby under JDKs 6 and 7
- Closed
-
DERBY-6854 Make it possible to run Derby tests on early access versions of JDK 9
- Open
-
DERBY-6855 Support JDBC changes introduced by Java 9
- Open
-
DERBY-6891 Investigate concurrency improvements to DerbyObservable and DerbyObserver
- Open