maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thorsten Glaser (JIRA)" <>
Subject [jira] [Commented] (MRESOURCES-237) Resource plugin's handling of symbolic links changed in 3.0.x, broke existing behavior
Date Thu, 04 Oct 2018 19:01:00 GMT


Thorsten Glaser commented on MRESOURCES-237:

Then, a new version which has a boolean parameter keepSymlinks or something like that would
be welcome. As I said, I’d have preferred a default of false, but a default of true is ok
as long as I can change this… I see now that newer maven-ear-plugin versions use maven-resources-plugin
3.x so this has become somewhat of a blocker of updating other plugins.

> Resource plugin's handling of symbolic links changed in 3.0.x, broke existing behavior
> --------------------------------------------------------------------------------------
>                 Key: MRESOURCES-237
>                 URL:
>             Project: Maven Resources Plugin
>          Issue Type: Bug
>    Affects Versions: 3.0.0, 3.0.1, 3.0.2
>         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-
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.9.11-200.fc25.x86_64", arch: "amd64", family: "unix"
>            Reporter: Brian D. Johnson
>            Priority: Minor
> 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.

This message was sent by Atlassian JIRA

View raw message