-
Notifications
You must be signed in to change notification settings - Fork 357
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
An issue has occurred with pitest-maven:1.17.0:report report, skipping LinkageError null, please report an issue to Maven dev team. #1358
Comments
The issue looks to be that something in apache commons is trying (and failing) to parse the current Java version. It's not clear why anything here needs to know the Java version - the code looks to be being called by some kind of reflective toString builder called by some user contributed code. I'll see if that can be easily stripped out. Can you confirm the exact build and version of java this is occurring on? |
Thank you for looking into this @hcoles . Here is the snippet from my pom file:
And here is the java I am using:
It is fairly recent java, I hope this is not causing problem |
The reflection based toString generator fails on some modern jvms as apache commons tries to parse out the version of Java, but fails due to outdated assumptions. Not clear why it's inmportant to have a toString method here, but replacing with an autogenerated one should solve #1358. Implementation excludes logger and sink form toString as it's unclear how they would be useful.
The reflection based toString generator fails on some modern jvms as apache commons tries to parse out the version of Java, but fails due to outdated assumptions. Not clear why it's inmportant to have a toString method here, but replacing with an autogenerated one should solve #1358. Implementation excludes logger and sink form toString as it's unclear how they would be useful.
Hello team,
Just wanted to say this project is awesome.
I am using the pitest maven plugin, to run pitest as part of the build pipeline process.
During the run, I am always faced with:
Apologies for the big copy-paste. As I do not know what is needed to further debug this issue, could you please let me know what I can provide to help resolve it?
Thank you for being so helpful
The text was updated successfully, but these errors were encountered: