Keep same classpath order as surefire #450
Merged
Conversation
This file contains 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
The elements' order on the classpath for native-image building must be consistent with the testing time when the graalvm agent is enabled to record the native image configurations.
oracle-contributor-agreement
bot
added
the
OCA Verified
melix
approved these changes
Jun 19, 2023
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.
The elements' order on the classpath for native-image building must be consistent with the testing time when the graalvm agent is enabled to record the native image configurations.
Different classpath order may lead to different classes that have the same name are loaded at agent recording time and native image building time. The two versions of the same name class can have different reflections. In this case, the different order will lead to native image runtime error.