Removed API is a blocking issue that has to be addressed before you tryĭependency analyzer. Updated jar file? Do you need to log an issue to address the use of deprecated API? Use of Use of deprecated API is not a blocking issue, but is something to look into. Jdeprscan looks for use of deprecated or removed API. You can assess the transition effort without having to recompile. These tools can be run against existing class or jar files. Java 11 has two tools, jdeprscan and jdeps, that are useful for sniffing out potential issues.
You should also consult other guides, such as the Issues that you may run into and recommendationsįor resolving them. This document touches on tools to inspect code. And there are additions and modifications to API that Improve startup, performance, memory usage, and provide better integration New features have been added andĮnhancements have been made since Java 8. Quickly as possible, just trying to run on Java 11 is often the best approach.įor a library, the goal will be to publish an artifact that is compiled and tested If the goal is to get an application up and running as In general, the approaches are to try to run on Java 11 without recompiling, or toĬompile with JDK 11 first. Internal API, changes to class loaders, and changes to garbage collection. Potential issues include removed API, deprecated packages, use of There's no one-size-fits-all solution to transition code from Java 8 to Java 11.įor a non-trivial application, moving from Java 8 to Java 11 can be a significantĪmount of work.
0 kommentar(er)
