-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'Warning: Illegal reflective access' #26
Comments
Let me guess: you're using Java 9 to run MS-GF+? This is a known issue, and there is little I can do about it beyond wait for the maintainers of MS-GF+ dependencies to appropriately update their own dependencies. This is also why the release notes for Release v2018.01.83 have this line, and a remark on warnings: Java 9 compatibility: add dependencies on com.sun.xml.bind:jaxb-impl and jaxb:activation to support use with Java 9 (with some warnings). Without this change, users must supply the Java VM argument "--add-modules=java.xml.bind,java.activation" |
Yes that's exactly right, I'm using 'openjdk version "9.0.4". I'm not entirely sure how you'd add those dependencies on com.sun.xml.bind:jaxb-impl and jaxb:activation ? If you have any guidelines or instructions for that they'd be greatly appreciated! So if those dependencies are not added, I can supply the argument to the main command for using MSGF+? Thank you! |
Well, the "add dependencies" portion was a change to the code so that you could still run MS-GF+ with Java 9, without needing to add extra text to the command line. The "(with some warnings)" is a reference to the warnings you saw, because there are going to be some changes in those, and so they might be errors with Java 10 instead of just warnings. |
Just a note, these warnings are still occurring with Java 12
We don't have a fix for this, but I'm including these here for reference nonetheless. |
Next release will have a fix for the warning messages (by depending on jaxb-runtime 2.3.1+ instead of jaxb-impl 2.2.7) |
Hello,
I'm experiencing the following warning:
I'm not really sure how to interpret this? Any advice is appreciated!
Thanks,
Scott
The text was updated successfully, but these errors were encountered: