Paolo, As most frameworks and platforms, Ignite contains low-level logic, which was changed in Java 9. For example, in Java 9 application classloader is not a UrlClassLoader anymore, while in ignite-hadoop we used methods from UrlClassLoader for implementing class loading logic.
So, --add-opens and other flags will not help right now, the community should do some changes in code first. Evgenii 2017-10-13 10:08 GMT+03:00 Paolo Di Tommaso <[email protected]>: > Hi, > > Any feedback would be appreciated. Thanks! > > On Thu, Oct 12, 2017 at 8:41 AM, Paolo Di Tommaso < > [email protected]> wrote: > >> Hi Denis, >> >> Neither in compatibility mode? I mean adding some --add-opens options >> <https://docs.oracle.com/javase/9/migrate/toc.htm#JSMIG-GUID-2F61F3A9-0979-46A4-8B49-325BA0EE8B66> >> to access deprecated/internal apis? >> >> Almost any any existing Java app works in this way. I've tried that but >> it seems Ignite is throwing an exception because the Java version number >> does not match the expected pattern. >> >> Any workaround ? >> >> Cheers, >> Paolo >> >> >> On Thu, Oct 12, 2017 at 1:25 AM, Denis Magda <[email protected]> wrote: >> >>> Hi Paolo, >>> >>> There is some work to do to make Ignite running on Java 9: >>> https://issues.apache.org/jira/browse/IGNITE-4615 >>> >>> Guess the version will be supported by the end of the year. >>> >>> — >>> Denis >>> >>> On Oct 11, 2017, at 2:08 PM, Paolo Di Tommaso <[email protected]> >>> wrote: >>> >>> Hi, >>> >>> Which the minimal Ignite version that can run on Java 9 ? >>> >>> I'm trying Ignite 1.9 and I'm getting >>> >>> >>> Caused by: java.lang.IllegalStateException: Ignite requires Java 7 or >>> above. Current Java version is not supported: 9 >>> at org.apache.ignite.internal.IgnitionEx.<clinit>(IgnitionEx.java:185) >>> >>> >>> >>> >>> Thanks, >>> Paolo >>> >>> >>> >> >
