-
Notifications
You must be signed in to change notification settings - Fork 115
Upgrade from JDK8
-
JDK versions
Since JDK9, new version string schema is introduced by JEP 223, which put changes tojava -versionoutput and system properties. Some legacy version-checking code may have to be rewritten to support this new schema. -
Removed internal APIs
JEP 260 has hidden most of the JDK internal APIs from Java developers since JDK9, you may have to adjust your code to adapt, especially forUnsafe. -
GC log
Command line options and output format of GC logs have changed, tools and libraries depending on GC log format may have to be updated. See JEP 271 for more information -
Removed JavaEE APIs and CORBA modules
Java EE and CORBA modules have been removed by JEP 320, if your project depends on such APIs, you may want to check Jarkata EE project for upgrading. -
JDK directory layout
There's noJDK/jredirectory any more.
You can find more information on JDK9 Release Notes and JDK11 Release Notes
If a software supports Java11, it should support Dragonwell 11 as well.
| name | minimum version |
|---|---|
| Spring Boot | 2.1.0 |
| Spring | 5.1 |
| Intellij | 2019.1 |
| Eclipse | 4.9 |
| Tomcat | 9.0 |
| Jetty | 9.4.13 |
| Netty | 4.1.30 |
| Maven | 3.5.0 |
| Maven compiler plugin | 3.8.0 |
| Gradle | 5.0 |
| ASM | 7.0 |
| Guava | 19.0 |
Please let us know if you have more libraries to add here.
-
jdepshas been included in JDK8 (jdk8/bin/jdeps) to help with resolving module dependencies, usage of JDK internal APIs, etc. Please check out its documentation for detailed usage. - IBM has provided Migration Toolkit for Application Binaries, please checkout this guide for detailed steps.