-
Notifications
You must be signed in to change notification settings - Fork 312
Illegal character in path when classpath contains entry with URL-encoded space #414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
eriklumme
pushed a commit
to eriklumme/ArchUnit
that referenced
this issue
Aug 28, 2020
When using the non-raw getSchemeSpecificPart() method on an URI, it will no longer be escaped, and the subsequent call to URI#resolve may fail. Signed-off-by: Erik Lumme <erik.lumme@gmail.com>
eriklumme
pushed a commit
to eriklumme/ArchUnit
that referenced
this issue
Aug 28, 2020
When using the non-raw getSchemeSpecificPart() method on an URI, it will no longer be escaped, and the subsequent call to URI#resolve may fail. Signed-off-by: Erik Lumme <erik.lumme@gmail.com>
eriklumme
pushed a commit
to eriklumme/ArchUnit
that referenced
this issue
Aug 31, 2020
When using the non-raw getSchemeSpecificPart() method on an URI, it will no longer be escaped, and the subsequent call to URI#resolve may fail. Signed-off-by: Erik Lumme <erik@vaadin.com>
codecholeric
added a commit
that referenced
this issue
Sep 5, 2020
When using the non-raw getSchemeSpecificPart() method on an URI, it will no longer be escaped, and the subsequent call to URI#resolve may fail. Resolves #414
codecholeric
pushed a commit
that referenced
this issue
Feb 21, 2021
When using the non-raw getSchemeSpecificPart() method on an URI, it will no longer be escaped, and the subsequent call to URI#resolve may fail. Signed-off-by: Erik Lumme <erik@vaadin.com>
codecholeric
added a commit
that referenced
this issue
Feb 21, 2021
When using the non-raw getSchemeSpecificPart() method on an URI, it will no longer be escaped, and the subsequent call to URI#resolve may fail. Resolves #414
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yes, it looks like another Windows URI issue.
Running tests from IntelliJ I get the error below. It is only logged as a warning, and the tests still run successfully. However, with some ~20 instances of that stack trace, it pollutes the logs quite a bit.
Interesting, too, that the path seems to be URL encoded initially:
Cannot parse URL classpath entry [...]/Program%20Files/[...]
[...] Illegal character in path at index 11: [...]/Program Files/[...]
ArchUnit version
0.14.1
, Junit 5.The text was updated successfully, but these errors were encountered: