You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a simple riemann-clojure-client client under Java 10, I see these warnings:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.protobuf.UnsafeUtil (file:/home/pmadden/.m2/repository/com/google/protobuf/protobuf-java/3.5.1/protobuf-java-3.5.1.jar) to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of com.google.protobuf.UnsafeUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
I suppose that this might be related to protocolbuffers/protobuf#3781, and might be fixed in a newer protocolbuffers release. I also suspect that this might be more appropriate to riemann-java-client, but I'm not sure.
Steps to reproduce:
Start up a default Riemann server as described in http://riemann.io/quickstart.html, up to and including the bin/riemann etc/riemann.config command.
If I add an explicit [com.google.protobuf/protobuf-java "3.7.1"] dependency to my project.clj, the warnings disappear -- though I don't know yet if the Riemann client will function correctly with this version.
The text was updated successfully, but these errors were encountered:
When running a simple
riemann-clojure-client
client under Java 10, I see these warnings:I suppose that this might be related to protocolbuffers/protobuf#3781, and might be fixed in a newer
protocolbuffers
release. I also suspect that this might be more appropriate toriemann-java-client
, but I'm not sure.Steps to reproduce:
bin/riemann etc/riemann.config
command.lein run
in this directory:If I add an explicit
[com.google.protobuf/protobuf-java "3.7.1"]
dependency to myproject.clj
, the warnings disappear -- though I don't know yet if the Riemann client will function correctly with this version.The text was updated successfully, but these errors were encountered: