[ https://issues.apache.org/jira/browse/SUREFIRE-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17792647#comment-17792647 ]
ASF GitHub Bot commented on SUREFIRE-2211: ------------------------------------------ robseidel commented on PR #689: URL: https://github.com/apache/maven-surefire/pull/689#issuecomment-1837898208 I've now restored the commit message. > additionalClasspathElement with UNC path not working with Maven Failsafe > Plugin > ------------------------------------------------------------------------------- > > Key: SUREFIRE-2211 > URL: https://issues.apache.org/jira/browse/SUREFIRE-2211 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin > Affects Versions: 3.0.0-M2, 3.2.2 > Environment: Windows JDK17.0.5+8 > Reporter: Robert Seidel > Assignee: Michael Osipov > Priority: Major > Fix For: 3.2.3 > > > We are using the configuration parameter additionalClasspathElements > (https://maven.apache.org/surefire/maven-failsafe-plugin/integration-test-mojo.html#additionalClasspathElements) > to provide a log4j2 xml configuration during tests. There is configured an > UNC path like this //our-server/build/failsafe containing the file. > Until version 3.0.0-M2 everything was fine, the ressource could be found > within the class loader and log4j was configured correctly (so 3.0.0-M1 was > ok). > However since the Milestone 2 of version 3 and with all later versions, the > ressource could not be found within the classpath, leaving log4j unconfigured. > From the reporting xml the classpath is configured the same, but the class > loader behaves differently. > When using a normal path like c:/build/failsafe the ressource can be found > without issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)