Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Java 9 compatibility

See original GitHub issue

java.lang.IllegalAccessError: class net.openhft.chronicle.core.OS (in unnamed module @0x42d1c1ef) cannot access class sun.nio.ch.FileChannelImpl (in module java.base) because module java.base does not export sun.nio.ch to unnamed module @0x42d1c1ef
        at net.openhft.chronicle.core.OS.<clinit>(OS.java:67)

Java:

java version "9-ea"
Java(TM) SE Runtime Environment (build 9-ea+124)
Java HotSpot(TM) 64-Bit Server VM (build 9-ea+124, mixed mode)

Issue Analytics

State:
Created 7 years ago
Comments:20 (17 by maintainers)

Top GitHub Comments

1reaction

epickrramcommented, Sep 15, 2017

Not so much a roadmap, more a need to make sure that all the OpenHFT projects build/execute on JDK9.

Since I don’t really know what all the problems are going to be yet, it’s hard to figure out exactly what will be required.

If you’d like to help, then discovering and raising issues against the OpenHFT projects would be a good start. Feel free to fix any problems you find 😉

In terms of ordering, projects should be validated in the order that they appear in this file:

https://github.com/OpenHFT/OpenHFT/blob/master/chronicle-bom/pom.xml#L43

We’ll want to first deal with any breaking API changes (i.e. the char[] -> bytes[] change), so that the code can run on either Java8 or Java9. Any Java9-specific features will end up as a Jigsaw module for Java9 in this repo:

https://github.com/OpenHFT/Chronicle-JDK9

1reaction

epickrramcommented, Aug 30, 2017

Hi @MartyIX I’ll be picking this work up shortly. I’ll review your changes and get back to you.