fix: resolve %20-encoded spaces in classpath resource paths - #227
Open
YoungMind1 wants to merge 1 commit into
Open
fix: resolve %20-encoded spaces in classpath resource paths#227YoungMind1 wants to merge 1 commit into
YoungMind1 wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Disclaimer: I have used AI for this PR.
When the repository is cloned into a directory whose name contains spaces (e.g. ~/my projects/cloudsim),
ClassLoader.getResource(name).getPath()returns a URL path string with those spaces encoded as %20. Passing thatstring directly to new File(...) or to file-reading APIs fails silently or with a
NullPointerException, because the literal %20 is not a valid filesystem path component.Symptoms:
• mvn clean install fails in
UtilizationModelPlanetLabInMemoryTestwith a test error.• Running any power/planetlab, container, or network example crashes immediately (I ran them via java -cp 'dependency list' classpath
Paths.get()only understands file: URIs. When running from a JAR, toURI() returns a jar:file:/... URI — and thedefault NIO filesystem provider doesn't know how to handle it. hence URLDecoder is used