Resolve parsing issue for module-info classes with multiple exports#4962
Conversation
|
@johannescoetzee Can you approve this PR? |
johannescoetzee
left a comment
There was a problem hiding this comment.
@mrjameshamilton Good catch! This looks good to me, so can be merged once the PR tests have passed. Thanks for the contribution :)
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4962 +/- ##
===============================================
+ Coverage 58.657% 58.659% +0.001%
Complexity 2564 2564
===============================================
Files 699 699
Lines 40121 40120 -1
Branches 7314 7314
===============================================
Hits 23534 23534
Misses 13620 13620
+ Partials 2967 2966 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
Great, thanks! There were unrelated formatting issues, I've run |
|
Apologies for the formatting issues. It was my fault for not doing what was necessary. |
When using version 3.28.0, I encountered the following exception when parsing the
module-info.classfrom a jar (junit-jupiter-api-5.11.4.jar):The cause of the issue is the parsing of the module file in the
JavassistModuleHelperclass. This PR fixes the parsing issue and updates the example in test resources to include multiple exports, exportsTo and an opens entry (the updated sample would trigger the same NPE).