Fix AbstractArchiver.getFiles() to return forward slashes for ZIP-based archivers #392
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.
Problem
The ZIP file specification requires that entry names use forward slashes (
/
) as path separators. However,AbstractArchiver.getFiles()
was returning entry names with platform-specific separators (e.g., backslashes\
on Windows). While the actual ZIP files were created correctly with forward slashes (normalized inAbstractZipArchiver.addResources()
), thegetFiles()
method returned inconsistent results that didn't match the actual archive entry names.This caused issues when users called
getFiles()
to inspect archive entries before creation, as they would see platform-specific paths instead of the normalized paths that would appear in the final ZIP file.Solution
This PR overrides
getFiles()
inAbstractZipArchiver
to normalize path separators to forward slashes, ensuring consistency between the returned map and the actual ZIP entry names.Example
Before this fix on Windows:
After this fix:
Changes
getFiles()
that normalizes all path separators to forward slashesImpact
ZipArchiver
,JarArchiver
, and subclassesFixes #244
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.