JDK Internal API Usage Report for aspectj-1.8.2

["Rory O'Donnell Oracle, Dublin Ireland" <rory.odonnell@xxxxxxxxxx>]

On 15/09/2014 09:41, Rory O'Donnell Oracle, Dublin Ireland wrote:

Hi Andy,

As part of the preparations for JDK 9, Oracle’s engineers have been analyzing open source projects like yours
to understand usage. One area of concern involves identifying compatibility problems, such as reliance on
JDK-internal APIs.

Our engineers have already prepared guidance on migrating some of the more common usage patterns of
JDK-internal APIs to supported public interfaces. The list is on the OpenJDK wiki [0], along with instructions
on how to run the jdeps analysis tool yourself .

We have analyzed jar files within aspectj-1.8.2 and found 0 jar files depending on JDK-Internal-APIs.

However, jdeps is a static analysis tool and therefore use of JDK-internal APIs via reflection or dynamically
generated bytecode are not reported by the tool, while such a dependency should also be replaced.

If you have any feedback please reply either on this list or to me directly.

Rgds,Rory

[0] https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool

-- 
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland 

The HTML attachment was scrubbed, report below.

JDK Internal API Usage Report for aspectj-1.8.2

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 aspectj-1.8.2:

• Numer of jar files depending on JDK-internal APIs: 0
• Internal APIs that have known replacements: 0
• Internal APIs that your team should migrate away: 0

APIs that have known replacements:

ID	Replace Usage of	With	Inside

JDK-internal APIs without supported replacements:

ID	Internal APIs (do not use)	Used by

Identify External Replacements

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

ID	Internal API (grouped by package)	Used By	Identify External Replacement

-- 
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland