Hello Alexey, There is a JIRA issue covering Java 9 support: https://issues.apache.org/jira/browse/BEAM-2530
The goal of this JIRA is to update the project to support the current Beam features with Java 9 (we need to keep our current level of backwards compatibility with Java >= 7). Migration to the new module system is not part of this JIRA and probably will be something to consider once this first step is done. This JIRA will be complete when we can take the Beam source code and compile/test/use all the artifacts with Java 9. Unfortunately we need changes not only in the Beam source code but also on the full dependencies we use from Maven plugins (enforcer, compiler, etc) to other libraries, e.g. Google AutoValue, ByteBuddy/ASM, etc. If you are interested in helping with this issue (or any other person in the community) contributions are welcomed, if the fix you propose works and is backwards compatible please feel free to open a new Pull Request. Regards, Ismaël On Sun, Sep 10, 2017 at 9:37 PM, Alexey Demin <[email protected]> wrote: > Hi > > Do you have plan for support java 9 in nearest future? > > In beam's runners you have code like: > > if (classloader instanceof URLClassLoader) { > URLClassLoader urlClassLoader = (URLClassLoader) classloader; > for (URL url : urlClassLoader.getURLs()) { > > only for extract list of jars from classpath. > but in java 9 jdk.internal.loader.ClassLoaders$AppClassLoader not extend > URLClassLoader. > > why not use System.getProperty("java.class.path") if we need only list of > jars from classpath? > > yes, this code not work correctly with enabled modules system, > but he work without any problem with default parameters for java 9. > > I tried run examples and they worked correctly on java 9 runtime. > > Thanks, > Alexey
