We definitely can't backport an API change.
Reading the bug report it seems they have been doing this by using
internal APIs.
For JDK 9, since illegal-access is allowed by default, they can continue
to do that,
so perhaps we can just not worry about the backport and solve this only
for 10 +
They can add reflective code to look for the 10 solution so it can run
on all releases
and automatically take advantage of the new API when it appears.
Of course they should also re-work the existing code to be reflective
and defer
to the new API. If they do this then it would also be safe when illegal
access is denied by default ..
since it should be in a later release than the new API.
-phil
On 9/28/17, 11:02 AM, Semyon Sadetsky wrote:
On 9/28/2017 10:51 AM, Philip Race wrote:
If this is up for consideration for backporting - as appears to be
the case - then
I think you should post an updated webrev.
Not sure that we can backport it because this would change the API.
--Semyon
-phil.
