JDK Internal API Usage Report for infinispan-6.0.2.Final-all

The OpenJDK Quality Outreach campaign has run a compatibility report to identify usage of JDK-internal APIs. Usage of these JDK-internal APIs could pose compatibility issues, as the Java team explained in 1996. We have created this report to help you identify which JDK-internal APIs your project uses, what to use instead, and where those changes should go. Making these changes will improve your compatibility, and in some cases give better performance.

Migrating away from the JDK-internal APIs now will give your team adequate time for testing before the release of JDK 9. If you are unable to migrate away from an internal API, please provide us with an explanation below to help us understand it better. As a reminder, supported APIs are determined by the OpenJDK's Java Community Process and not by Oracle.

This report was generated by jdeps through static analysis of artifacts: it does not identify any usage of those APIs through reflection or dynamic bytecode. You may also run jdeps on your own if you would prefer.

Summary of the analysis of the jar files within infinispan-6.0.2.Final-all:

• Numer of jar files depending on JDK-internal APIs: 10
• Internal APIs that have known replacements: 0
• Internal APIs that have no supported replacements: 73

APIs that have known replacements:

JDK-internal APIs without supported replacements:

Identify External Replacements

You should use a separate third-party library that performs this functionality.