Hi Andreas,
We hadn't run the tool against any of your releases, so thanks for all your
help.
Rgds,Rory
On 25/06/2015 21:58, Andreas Veithen wrote:
I tested this with the current trunk, which basically has no code
changes compared with 3.0.3. Wouldn't it be good to include the
version number of the release you tested against in the mails you send
to projects?
Andreas
On Mon, Jun 22, 2015 at 8:04 AM, Rory O'Donnell
<[email protected]> wrote:
Hi Andreas,
That means Apache Neethi has no internal dependencies, thanks for that.
Can you tell me what version of Apache Neethi you checked?
At https://wiki.openjdk.java.net/display/Adoption/JDK+9+Outreach you can
find a (preliminary) list of
other changes that might affect your project's code in JDK 9, and other
things to consider when testing
with JDK 9.
If you are already testing with JDK 9, and have run into other issues,
please let us know! If you haven't
done so yet, and would like to start, our Quality Outreach effort [0] is a
good way to get started, get
regular updates on new builds to test and what to check for, and get help
navigating the JDK development
process, from filing issues to providing feedback.
Rgds,Rory
[0] https://wiki.openjdk.java.net/display/quality/Quality+Outreach
On 20/06/2015 21:07, Andreas Veithen wrote:
Not sure what they are referring to. Tested this on the current
snapshot version and jdeps didn't report anything.
Andreas
On Fri, Jun 19, 2015 at 11:21 AM, Rory O'Donnell
<[email protected]> wrote:
Hi Sagara,
My name is Rory O'Donnell, I am the OpenJDK Quality Group Lead.
I'm contacting you because your open source project seems to be a very
popular dependency for other open source projects.
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].
As part of the ongoing development of JDK 9, I would like to inquire
about
your usage of JDK-internal APIs and to encourage migration towards
supported Java APIs if necessary.
The first step is to identify if your application(s) is leveraging
internal
APIs.
Step 1: Download JDeps.
Just download a preview release of JDK8(JDeps Download). You do not need
to
actually test or run your application on JDK8. JDeps(Docs) looks through
JAR files and identifies which JAR files use internal APIs and then lists
those APIs.
Step 2: To run JDeps against an application. The command looks like:
jdk8/bin/jdeps -P -jdkinternals *.jar > your-application.jdeps.txt
The output inside your-application.jdeps.txt will look like:
your.package (Filename.jar)
-> com.sun.corba.se JDK internal API (rt.jar)
3rd party library using Internal APIs:
If your analysis uncovers a third-party component that you rely on, you
can
contact the provider and let them know of the upcoming changes. You can
then
either work with the provider to get an updated library that won't rely
on
Internal APIs, or you can find an alternative provider for the
capabilities
that the offending library provides.
Dynamic use of Internal APIs:
JDeps can not detect dynamic use of internal APIs, for example through
reflection, service loaders and similar mechanisms.
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
--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin,Ireland
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
