The only issue is we need something like these: hope this help you --add-exports jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.model=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.processing=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED --add-opens jdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED --add-opens jdk.compiler/com.sun.tools.javac.comp=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.util.concurrent=ALL-UNNAMED --add-opens java.base/java.util.concurrent.locks=ALL-UNNAMED --add-opens java.base/java.text=ALL-UNNAMED --add-opens java.base/java.net=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.util.concurrent.atomic=ALL-UNNAMED --add-opens java.base/java.util.regex=ALL-UNNAMED --add-opens java.base/java.nio=ALL-UNNAMED --add-opens java.base/jdk.internal.misc=ALL-UNNAMED --add-exports java.base/sun.net.www.protocol.https=ALL-UNNAMED --add-exports java.base/sun.util.calendar=ALL-UNNAMED --add-exports java.base/java.lang.reflect=ALL-UNNAMED --add-opens java.base/sun.net.util=ALL-UNNAMED --add-opens java.base/sun.nio.ch=ALL-UNNAMED --add-opens java.base/java.math=ALL-UNNAMED --add-opens java.base/sun.security.action=ALL-UNNAMED --add-opens java.management/sun.management=ALL-UNNAMED --add-opens java.sql/java.sql=ALL-UNNAMED
何品 PJ Fanning <fannin...@gmail.com> 于2024年6月18日周二 21:02写道： > I've added Java 17 and 21 testing and only 1 minor testing issue with > mockito was found that is easily worked around. > > Nicolas and Chris have also replied on this thread confirming that > pekko-management works ok in Java 17. > > > On Tue, 18 Jun 2024 at 12:14, Sharath Reddy > <sharath.reddy.boyapa...@gmail.com> wrote: > > > > Hi PJ, > > > > Currently, we are using Akka and JDK 17. > > We had planned to migrate to Pekko only if it supports JDK 17, so we > might > > not be able to try and test it at this time. > > > > Regards, > > Sharath. > > > > On Tue, Jun 18, 2024 at 2:54 PM PJ Fanning <fannin...@gmail.com> wrote: > > > > > Hi Sharath, > > > We don't run CI testing for Java 17. At the same time, the Java team > > > are very careful about compatibility in their releases. > > > Have you tried running with Java 17? If not, could you try? If you > > > find some issues, could you report them as bugs? > > > > > > Regards, > > > PJ > > > > > > On Tue, 18 Jun 2024 at 07:15, Sharath Reddy > > > <sharath.reddy.boyapa...@gmail.com> wrote: > > > > > > > > Hello Pekko Community, > > > > > > > > We are currently using Akka 2.6.x and planning to migrate to Pekko. > > > > However, we've encountered an issue: **pekko-management** doesn't yet > > > > support JDK 17. We'd appreciate any insights or workarounds from the > > > > community. > > > > > > > > 1. **Current Setup**: > > > > - Akka version: 2.6.x > > > > - JDK: 17 > > > > > > > > 2. **Questions**: > > > > - Has anyone successfully migrated from Akka to Pekko with JDK 17? > > > > - Are there any known compatibility issues? > > > > - Is there a recommended approach for handling this situation? > > > > > > > > Any advice, experiences, or pointers would be greatly appreciated! > > > > > > > > Thank you, > > > > Sharath > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > > > For additional commands, e-mail: dev-h...@pekko.apache.org > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > For additional commands, e-mail: dev-h...@pekko.apache.org > >
