[JEP 403] Use case for a new standard replacement

[Remi Forax]

> From: "Kumar Ashish" <kr.ashish8196 at gmail.com>
> To: jigsaw-dev at openjdk.org
> Sent: Monday, August 8, 2022 11:17:59 PM
> Subject: [JEP 403] Use case for a new standard replacement

> Hi,
> I have been using [ https://github.com/uber/cadence-java-client |
> https://github.com/uber/cadence-java-client ] in my service, and it contains
> two illegal access operations. I am trying to upgrade to java 17 in my service,
> but am unable to do so because of these operations. These operations have been
> mentioned in this issue, [
> https://github.com/uber/cadence-java-client/issues/647 |
> https://github.com/uber/cadence-java-client/issues/647 ] . I am not sure if
> this has already been queried but what should I do to solve this?

Hi, 
if you control the command line, you can use --add-opens, something like 
--add-opens java.base/java.lang=ALL-UNNAMED 

> Regards,
> Kumar Ashish

Rémi 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jigsaw-dev/attachments/20220808/f12d3282/attachment.htm>