Samuel Audet
Samuel Audet
That's probably not related to the Java version, but to one of your libraries incorrectly overriding the URL protocol.
I've just given JavaCPP a spin with Maven 3.8.4 and JDK 17! While I'm getting a java.lang.reflect.InaccessibleObjectException from the OSGi tests (@timothyjward Is OSGi incompatible with JDK 17?), apart from...
It wasn't designed for that, no... Check the README.md file for some options.
I'm not sure why ANTLR would help with that. We don't really need to parse anything... Am I missing something?
As mentioned in the `README.md` file, there's already solutions like [Jace](https://code.google.com/p/jace/) and [JunC++ion](http://codemesh.com/products/junction/) for that. What is missing from those two?
There's also jni.hpp these days: https://github.com/mapbox/jni.hpp
The only thing that makes a deamon thread different from a normal thread is that the JVM will terminate the process even when daemon threads are still running. If that's...
Some native libraries might not like it and crash the JVM. That's entirely possible.
So, in the end, have you encountered any issue?
What does the code look like?