Closed mibby closed 6 years ago
How do you call that "incompatibility"?
It seems to still work completely fine - its jsut a warning.
If this doesn't occur in BungeeCord it might be because of the Log4J addition.
https://github.com/apache/logging-log4j2/blob/master/log4j-api/src/main/java/org/apache/logging/log4j/util/StackLocator.java ~~ https://github.com/PaperMC/Waterfall/blob/master/BungeeCord-Patches/0037-Use-Log4j2-for-logging-and-TerminalConsoleAppender-f.patch
Ultimately not ideal, but java 11 is still new and many parts of the ecosystem are still behind, such as the library causing that warning; I'll leave this open for meta as a reminder to track upstream for fixes to this issue
I am running Lucene Indexing technique using JAVA 11 and got the same warning on google colab, however, it did not affect the performance a bit. It's just a warning and you can ignore it.
Please do not bump stone age issues without any proper reason. This issue has been solved long time ago.
Waterfall dev 227 Java 11
Recently migrated over to Java 11 since Java 8 is EOL. Noticed this warning coming from Waterfall during start-up initialization.