Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Analysis of commons-jelly-1.0 & commons-launcher-1.1 dependencies
 on JDK-Internal APIs
From: Paul Libbrecht <paul@hoplahup.net>
In-Reply-To: <54416485.4020607@oracle.com>
Date: Fri, 17 Oct 2014 21:20:14 +0200
Cc: Commons Developers List <dev@commons.apache.org>,
 britter@apache.org,
 Vaidya Balchandra <Balchandra.Vaidya@oracle.com>,
 "TOPIC,DALIBOR" <dalibor.topic@oracle.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <AF5A7ADB-95CA-4108-BD4E-69297AB70B78@hoplahup.net>
References: <5440D682.3030000@oracle.com>
 <33C86D6F-F4DE-4C05-9F3E-F1DE27EA44E9@hoplahup.net>
 <54416485.4020607@oracle.com>
To: "Rory O'Donnell" <rory.odonnell@oracle.com>

Thanks Rory,

why would org.w3c.* or org.relaxng.* be JDK internal?

Does it mean=85 it's going to be included in JDK 9? (probably as a =
conflicting version with some priority to included jars thus maybe =
breaking) ?

Those are trusted software providers since years (Jelly is quite old).

paul

On 17 oct. 2014, at 20:48, "Rory O'Donnell" <rory.odonnell@oracle.com> =
wrote:

> Let me try one at a time - commons-jelly attached.
>=20
> Rgds,Rory
> On 17/10/2014 19:22, Paul Libbrecht wrote:
>> Rory,
>>=20
>> I see no attachments here. Can you post it to some web-place please?
>>=20
>> paul
>>=20
>>=20
>> On 17 oct. 2014, at 10:42, Rory O'Donnell <rory.odonnell@oracle.com> =
wrote:
>>=20
>>> Hi Benedict,
>>>=20
>>> As I already mentioned we have 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 .
>>>=20
>>> I have prepared reports , attached to this email, for =
commons-jelly-1.0 & commons-launcher-1.1 based on the jdeps output.
>>>=20
>>> For anything where your migration path is unclear, I would =
appreciate comments on the JDK-internal API usage patterns in the =
attached jdeps reports - in particular comments elaborating on the =
rationale for them - either to me or on the adoption-discuss [1] mailing =
list at OpenJDK.
>>>=20
>>> Finding suitable replacements for unsupported interfaces is not =
always straightforward, which is why I am reaching out to you
>>> early in the JDK 9 development cycle so you can give feedback about =
new APIs that may be needed to facilitate this exercise.
>>>=20
>>> Thank you in advance for any efforts and feedback helping us make =
JDK 9 better.
>>>=20
>>> Rgds,Rory
>>>=20
>>> [0] =
https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool
>>> [1] http://mail.openjdk.java.net/mailman/listinfo/adoption-discuss
>>>=20
>>> --=20
>>> Rgds,Rory O'Donnell
>>> Quality Engineering Manager
>>> Oracle EMEA , Dublin, Ireland
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>> =
---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>=20
> --=20
> Rgds,Rory O'Donnell
> Quality Engineering Manager
> Oracle EMEA , Dublin, Ireland
>=20
> <JDK Internal API Usage Report for commons-jelly-1.0.html>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org