[ 
https://issues.apache.org/jira/browse/MRESOURCES-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634274#comment-17634274
 ] 

David Causse commented on MRESOURCES-269:
-----------------------------------------

I can confirm that there is still an issue with symlinks and the 3.3.0 of the 
maven-resource-plugin, we still have to downgrade to 3.1.0 for our project to 
work:

Error is:
{code:java}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-resources-plugin:3.3.0:testResources 
(default-testResources) on project eventutilities: copying 
/srv/nomoa_dev/event-platform/wikimedia-event-utilities/eventutilities/src/test/resources/event-schemas/repo4/test/event/latest
 to 
/srv/nomoa_dev/event-platform/wikimedia-event-utilities/eventutilities/target/test-classes/event-schemas/repo4/test/event/latest
 failed with NoSuchFileException: 
/srv/nomoa_dev/event-platform/wikimedia-event-utilities/eventutilities/target/test-classes/event-schemas/repo4/test/event/latest
 -> [Help 1]
{code}
Please see 
[https://github.com/nomoa/wikimedia-event-utilities/blob/main/pom.xml#L256] 
where switching from 3.1.0 to 3.3.0 will cause the above problem.

 

> 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.10#820010)

Reply via email to