-
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
mzML Parser Class Fails to Initialize #18
Comments
This might be an issue with the version of java - I have yet to try running it with Java 9, it is compiled against the Java 6 baseline, and I have always run it under Java 7 and Java 8. Yes, it appears that Java 9 removed some classes that are used by the mzML/mzIdentML reader/writer dependencies used by MS-GF+. Please try running with Java 8 for confirmation. |
Yes, this is an issue of using too new a version of Java. Java 8 seems to work fine. |
I was able to resolve this issue by adding two new dependencies to MS-GF+, as of release v2018.01.30. They are marked as deprecated in Java 9, with plans to remove them in the future in favor of making them separate packages. The |
Hmm I'm on openJDK 11 with the 2017.07.21 and I get
Maybe the openJDK is too new? |
A change request removing java.xml.bind from the classes built-in to OpenJDK/Java 11 was accepted (it was deprecated as of OpenJDK/Java 9). This will likely mean that only MS-GF+ v2018.01.30 and newer will work with Java 11. The previous |
Attempting to run MS-GF+ under Java 9.0.1 on an mzML file produced by ProteoWizard MSConvert 30.11626 produces the following traceback:
While search can be performed if I use mzXML instead, when attempting to write the mzIdentML file a similar error:
This appears to be resolved by adding
--add-modules java.xml.bind
to the java command line argument list before the jar file. Am I using an unsupported version of Java or can this be added to the build step to remove the need to specify it at run time?The text was updated successfully, but these errors were encountered: