Uploaded image for project: 'Maven Resources Plugin'
  1. Maven Resources Plugin
  2. MRESOURCES-237

Resource plugin's handling of symbolic links changed in 3.0.x, broke existing behavior

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Reopened
    • Minor
    • Resolution: Unresolved
    • 3.0.0, 3.0.1, 3.0.2, 3.1.0, 3.2.0
    • 3.3.0
    • None
    • None

    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.

      Attachments

        1. a.tgz
          1 kB
          Thorsten Glaser

        Issue Links

          Activity

            People

              Unassigned Unassigned
              brianjohnson Brian D. Johnson
              Votes:
              6 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated: