Closed
Conversation
Change bytecode handling to explicitly fail rather than assume a type in switch cases Use objenesis instead of direct sun reflection-factory for instance creation Remove junit platform exclusion, resolving some failures with IntelliJ integration
This was referenced Oct 6, 2022
|
HI @rliesenfeld , @idstein , @gliptak Need your help to review / merge this PR, thanks |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
NOTE: The work on this PR and a few others is mirrored on https://github.com/hazendaz/jmockit1/ since it seems like the maintainers of this project are MIA
Encountered some compatibility issues with a project due to outdated bytecode handling. This PR addresses the cases I've encountered personally but should also address the following issues:
com.github.hazendaz.jmockit:jmockit:1.49.2which is mentioned in the thread though I could not find @hazendaz hosting the source currently)Other changes under the hood:
pom.xml, resolving some failures with IntelliJ integrationTesting
You can test the validity of the changes within this project by forcing maven to execute the project in a Java 11+ context. I suggest the maven toolchain plugin for this:
I tested up to Java 17 with all tests passing.