Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Date: Thu, 8 Dec 2016 23:32:58 +0000 (UTC)
From: "Tibor Digana (JIRA)" <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.13026345.1481114799000.478334.1481239978343@Atlassian.JIRA>
In-Reply-To: <JIRA.13026345.1481114799000@Atlassian.JIRA>
References: <JIRA.13026345.1481114799000@Atlassian.JIRA> <JIRA.13026345.1481114799015@arcas>
Subject: [jira] [Commented] (SUREFIRE-1312) Classpath containing url special
 characters with Reflections not working
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 08 Dec 2016 23:33:00 -0000


    [ https://issues.apache.org/jira/browse/SUREFIRE-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733724#comment-15733724 ] 

Tibor Digana commented on SUREFIRE-1312:
----------------------------------------

[~yanicks90]
Are you able to reproduce it with Version 2.19.1?
The class {{ForkClient}} and classpath configuration in it is responsible for setting system property {{java.class.path}} is set with value but maybe not decoded properly.
Do  you want to open PR in GitHub?

> Classpath containing url special characters with Reflections not working
> ------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1312
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1312
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: classloading
>    Affects Versions: 2.16
>         Environment: windows 7, RHEL 7
>            Reporter: Yanick Salzmann
>            Assignee: Tibor Digana
>
> When using the maven surefire plugin with unit tests that make use of the {{CdiRunner}} (which internally fires up a Weld context) I am facing problems with classpaths that contain characters that need url encoding.
> I have created the following debug output in my test class in the {{@BeforeClass}} method:
> {code}
> System.out.println("----WELD-TEST----");
> System.out.println(ConverterTest.class.getClassLoader().getResource("."));
> System.out.println("----WELD-TEST-END----");
> {code}
> This prints the following output: {{file:/C:/sources%402/parser/target/test-classes/}}
> When the tests are launched from IntelliJ the output looks like this: {{file:/C:/sources@2/parser/target/test-classes/}}
> Note the @2 versus %402. In the end this causes Reflections (used by Weld) to fail, because it attempts to urlencode the classpath and ends up with {{file:/C:/sources%25402/parser/target/test-classes/}} and gets exceptions when attempting to read files and directories.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)