[SUREFIRE-2211] additionalClasspathElement with UNC path not working with Maven Failsafe Plugin

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-M2, 3.2.2
• Fix Version/s: 3.2.3
• Component/s: Maven Failsafe Plugin
• Environment: Windows JDK17.0.5+8

Language

Java

• Assignee: Michael Osipov
• Reporter: Robert Seidel
• Created: 17/Nov/23 08:35
• Updated: 04/Dec/23 12:29
• Resolved: 04/Dec/23 12:29

Description

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.

Issue Links

• links to: GitHub Pull Request #689