Hi, Sorry for replying late here, not sure if you already did these changes, but the code in CleanerUtil tries to handle this gracefully with not cleaning on JDKs which do not support this.
There should be no compile-time dependency on any unsafe object, during runtime we try to get a cleaner and simply not unmap buffers cleanly if not possible for some reason. Which new problem do you see with this approach when using the JDK module system? Thanks... Dominik. On Mon, Jun 29, 2020 at 10:36 PM Andreas Beeker <kiwiwi...@apache.org> wrote: > Hi *, > > I'm facing the same problem as described in > https://issues.apache.org/jira/browse/LUCENE-6989 > > Is it ok for you, if I get our build more or less to run with the module > path (instead of the classpath) when running in a JDK 9+ and later try to > fix the above Cleaner problem? > > I simply would like to focus on one issue now and as we a have > multi-release jars after my commit, a JDK dependent solution shouldn't be a > problem anymore. > > Andi > > >
