Use escaped path in report-ng when accessing JAR #37
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.
Description
Previously the URI to the JAR file of report-ng was constructed using the unescaped path. This would fail if there are carecters in the path that are not valid in the path component of a URI (e.g. spaces). This pull request changes the construction of the URI to use the escaped path component and makes report-ng work with local maven repos that have spaces and other
special characters in their path.
Fixes #33
Type of change
Checklist:
Tested on Windows in Git Bash and on Ubuntu 20.04.