[GRADLE-1830] copy / archive tasks include redundant directories Created: 13/Oct/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Szczepan Faber Assignee: Unassigned
Resolution: Won't Fix Votes: 7


 Description   

When eachFile is used to manipulate file 'path' then often redundant empty folders are created.

Example:

-origin
\-dir1
 \file1
\file2

task copy(type: Copy) {
  from('origin') {
    eachFile { it.path = "someDir/$it.path" }
  }
  into('dest')
}

Expected:

-dest
\-someDir
 \dir1
  \file1
 \file2

Actual:

-dest
\-someDir
 \dir1
  \file1
 \file2
\dir1

E.g. redundant empty folder dir1. includeEmptyDirs flag does not have any effect on the case.

 Comments   
Comment by Luke Daley [ 20/Aug/12 ]

Related forum post: http://forums.gradle.org/gradle/topics/copyspec_support_for_moving_files_directories

Comment by David Pärsson [ 01/Aug/13 ]

Is there a suggested workaround for this? I guess deleting the directories in a doLast block would be an option when using the Copy task, but what about the Zip task?

Comment by Luke Daley [ 01/Aug/13 ]

The workaround there would be to use a copy task with a do last, then zip up the result of the copy task.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:05:30 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.