Copy task replacing symbolic link contents

Help/Discuss
1

The following behaviour was observed under Windows 10 and Gradle 8.14.

Assuming the following situation:

One directory with regular files, like text files.
A Second directory with symbolic links pointing to the files in the first directory.
A third directory with a Gradle project containing a custom task to copy files into the second directory.

tasks.register<Copy>("copyDirectoryContents") {
    from("docs")
    into("E:\\workspace\\gradle_copy_bug\\target_directory")
}

When performing the task and there is a symbolic link with the same name as a file from the project, instead of overriding the symbolic link with the regular file the content of the file where the symbolic links is pointing to is being replaced.

Before executing task:

|- dir_one
|  |- test.txt (with content: "Hello world!")
|- dir_two
|  |- test.txt (symbolic link pointing to dir_one/test.txt)
|- dir_three
|  |- docs
|     |- test.txt (with content: "Hello from Gradle directory!")

After executing task:

|- dir_one
|  |- test.txt (with content: "Hello from Gradle directory!")
|- dir_two
|  |- test.txt (symbolic link pointing to dir_one/test.txt)
|- dir_three
|  |- docs
|     |- test.txt (with content: "Hello from Gradle directory!")

Expected behaviour:

|- dir_one
|  |- test.txt (with content: "Hello world!")
|- dir_two
|  |- test.txt (with content: "Hello from Gradle directory!")
|- dir_three
|  |- docs
|     |- test.txt (with content: "Hello from Gradle directory!")

Simply deleting the target directory before the task is being called is unfortunately not an option, as there are other files in there that need to be preserved.

Is my expectation of that behaviour wrong or is there a possibility to configure the copy task to perform in the expected way?

2

Your observation is correct and unfortunately this is not currently configurable.
The Copy task uses FileOutputStream to write the copied file and that always goes to the target of symbolic links.

So what you can do is opening a feature request to make this configurable.
The newer java.nio APIs could be configured what to do with symbolic links.

As a work-around you can probably use eachFile { ... } and in there delete the path if it exists, so that when the actual copy is done, the symbolic link is gone already.

3

I will try the idea with the eachFile.
With that I should be able to deal with the problem.
Thank you very much (:

4

Might still warrant a feature request though even if you can work-around it. :slight_smile:
After you opened one, please post a link here for reference.