Double checked scripts and found some errors. Corresponding JIRA issue [1] fixed and merged to 2.4 release branch.
[1] https://issues.apache.org/jira/browse/IGNITE-7550 <https://issues.apache.org/jira/browse/IGNITE-7550> > On 26 Jan 2018, at 01:27, Denis Magda <dma...@apache.org> wrote: > > Pavel, it’s a good point. > > Peter, could you ensure that all Ignite scripts (ignite.sh/bat, > control.sh/bat, etc.) perform this auto detection of JVM 9 as well? Alex K. > please do the same for Visor and Web Console scripts. > > — > Denis > >> On Jan 25, 2018, at 1:58 AM, Pavel Tupitsyn <ptupit...@apache.org> wrote: >> >> I would add that to run Ignite on Java 9 without default scripts one has to >> use the following JVM options: >> >> --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED" >> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED >> >> --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED >> >> --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED >> >> Ignite.NET adds these options automatically when Java 9 is detected, no >> user steps required. >> >> Thanks, >> Pavel >> >> >> On Thu, Jan 25, 2018 at 12:53 PM, vveider <mr.wei...@gmail.com> wrote: >> >>> Hi, Igniters! >>> >>> >>> Ticket IGNITE-6730 [1] was merged to master (and ignite-2.4) and now we >>> have >>> preliminary support of Java 9, which includes: >>> - compilation with JDK9 with some constraints (scala-2.10 based modules >>> should be turned off) >>> - run with JRE9/JDK9 through default scripts (ignite.{sh|bat}) >>> >>> Also, temporary TC project for Ignite Tests on Java 9 [2] was prepared; >>> analysis of test problems and corresponding fixes is in progress. >>> >>> Please, be advised. >>> >>> >>> [1] https://issues.apache.org/jira/browse/IGNITE-6730 >>> [2] https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java9 >>> >>> >>> >>> -- >>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >>> >
