Fix PathMatchingResourcePatternResolver to handle absolute paths in JAR manifests #35732
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
Artur-
force-pushed
the
manifest-absolute-paths
branch
from
a2ce970 to
6e775c5
Compare
spring-projects-issues
added
the
status: waiting-for-triage
jhoeller
added
type: bug
|
@Artur- this looks good for inclusion in the 6.2.13 release on Nov 13. Could you please rebase your PR onto |
… in JAR manifests When JAR manifest Class-Path entries contain absolute paths (as Gradle creates on Windows for long classpaths), PathMatchingResourcePatternResolver incorrectly rejected them. Fixes spring-projects#35730 Signed-off-by: Artur Signell <artur@vaadin.com>
Artur-
force-pushed
the
manifest-absolute-paths
branch
from
6e775c5 to
089c627
Compare
|
Rebased |
jhoeller
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
When JAR manifest Class-Path entries contain absolute paths (as Gradle creates on Windows for long classpaths), PathMatchingResourcePatternResolver incorrectly rejected them.
Fixes #35730