[GRADLE-1671] Add a simple way to create empty folders in copy and archive tasks Created: 10/Jul/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-3
Fix Version/s: None

Type: Improvement
Reporter: Russ Egan Assignee: Unassigned
Resolution: Won't Fix Votes: 11


In CopySpecs, there is no way to create empty folders in the target directory or archive. I know the option was added to copy empty folders from the source, but it would also be helpful to have a simple way to construct empty folders in the target. It might look something like:

task tar(type: tar) {
   into('empty') {

The expected behavior would be to create an empty folder in the root of the tar named 'empty'.

This use case came up in our project because our distribution tars include empty 'log' folders, into which our application writes logs. We can work around (either application creates dynamically, or build file creates empty folder in a tmp location and copies from there), but this would be most convenient and readable.

Comment by Alex Aiezza [ 18/Jul/15 ]

Yes. This would be convenient.

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:01:28 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.