[
https://issues.apache.org/jira/browse/MRESOURCES-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17455231#comment-17455231
]
Jimisola Laursen commented on MRESOURCES-269:
---------------------------------------------
[~slachiewicz] It does not work for me. With the explicit dependency on
3.3.0-SNAPSHOT Maven succeeds without errors.
However, the _symbolic link_ of the file (log4j2.yml) is copied to
target/classes and _not_ the actual file.
The symbolic links now points to the wrong relative path and log4j2 therefore
does not pick it up.
Hence, I'm back to square 1. I would like for maven-resources-plugin to copy
the actual file to target/classes.
There seems to be inconsistency since another symbolic link that points to a
directory has all its content (5-6 files) copied to target/classes.
That is, actual directory structure is copied if sym link but just sym link if
it is a file. Is this correct or have I missed something?
> Symlinks cause copying resources to fail
> ----------------------------------------
>
> Key: MRESOURCES-269
> URL: https://issues.apache.org/jira/browse/MRESOURCES-269
> Project: Maven Resources Plugin
> Issue Type: Bug
> Affects Versions: 3.2.0
> Reporter: jks
> Assignee: Sylwester Lachiewicz
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: MRESOURCES-269.tar.gz, log.txt
>
>
> Copying a symlink fails if the target does not exist. If the symlink is
> relative the order that the resources are copied matter. If A points to B
> but A is copied before B the copying of A will fail with a non-helpful
> message "Failed to execute goal ... on project xxx: <file path here>".
>
> This started failing for me on 3.2.0 (and works on 3.1.0) but that might be
> because somewhere in the dependencies the traversal order changed somehow.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
