Hi Robert,Kristian,
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
I think the mailing list stripped the attachment
On Monday, 15 September 2014, Rory O'Donnell Oracle, Dublin Ireland
rory.odonn...@oracle.com wrote:
Hi Robert,Kristian,
As part of the preparations for JDK 9, Oracle's engineers have been
analyzing open source projects like yours to
Ok, here is the text. Rgds,Rory
JDK Internal API Usage Report for apache-maven-3.2.3
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
Hi Stephen,
One more time, hope this is ok.
Rgds,Rory
JDK Internal API Usage Report for apache-maven-3.2.3
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
So if I read your report correctly, our code uses guava, which
contains references to sun.misc.Unsafe. Actually it's sisu that uses
guava, not maven core itself.
Not too much we can do about that, other than consider throwing guava
out of sisu. As long as we're on a sub-1.8 minimum language
We can move to the newer version of guava. This was one of the reasons I
updated to the latest sisu, I was told it did not depend on any internal
guava apis any more. Of course, somebody will have to check what guava
version is compatible with JDK 9 before we upgrade.
--
Regards,
Igor
On
I was not suggesting changing guava, which I agree, is not our problem.
I was suggesting using more recent version of guava in maven, which only
we can do.
--
Regards,
Igor
On 2014-09-15, 7:42, Kristian Rosenvold wrote:
Guava is a general purpose library that contains quite a bunch of
stuff.
