[MRESOURCES-237] Resource plugin's handling of symbolic links changed in 3.0.x, broke existing behavior

• Type: Bug
• Status: Reopened
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 3.0.0, 3.0.1, 3.0.2, 3.1.0, 3.2.0
• Fix Version/s: 3.3.0

Environment

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T11:41:47-05:00)
Java version: 1.8.0_121, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.9.11-200.fc25.x86_64", arch: "amd64", family: "unix"

• Assignee: Unassigned
• Reporter: Brian D. Johnson
• Created: 02/Mar/17 18:07
• Updated: 05/Apr/24 12:47

Description

It looks like the handling of symbolic links in the maven-resources-plugin has changed in version 3.0.x. I'm submitting a JIRA because it breaks the previous behavior and I have not been able to find this documented anywhere as an intended change.

Use case: Multi-module maven project. We have a custom log4j2 configuration file we use during testing. Instead of maintaining this file in multiple src/test/resources directories, we instead maintain a single copy of the file at the project's root level and create symbolic links from each module's src/test/resources directory to the file using relative paths.

2.7 Behavior: the symlink was evaluated and the target file was copied to target/test-classes/.

3.0.x Behavior: the symlink is copied to target/test-classes/ verbatim. The symlink's relative path results in the symlink pointing to the wrong file location. The log4j2 configuration is not found.

Requested Change: Either revert to the original 2.7 behavior, or document the change and provide a configuration parameter to allow the legacy behavior.

Issue Links

• is related to: MSHARED-1004 Two (2) issues with symbolic links
• is related to: MRESOURCES-212 maven resource plugin does not preserve symlinks