Introduce @ForkedClassPath for testing unmodified class path #22710
Conversation
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
spring-projects-issues
added
the
status: waiting-for-triage
|
Test failure seems to be an unrelated classpath conflict in RSocket |
wilkinsona
added
type: task
wilkinsona
pushed a commit
that referenced
this pull request
Aug 12, 2020
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.
Hi,
#22696 made
ModifiedClassPathExtensionpublic. Rather than doing that, this PR introduces a new annotation@ForkedClassPaththat can be used instead. That seems also more consistent to the already existing@ClassPathExclusions&@ClassPathOverrides.Let me know what you think.
Cheers,
Christoph