[GRADLE-1389] Add ability to set owner and group on entries in tar files Created: 17/Feb/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

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


TarEntry supports setting the uid and gid on TarEntries, but there is no means to configure this.

Actually, it would be sufficient if TarCopySpecVisitor would have a hook that gave the copy spec access to the TarEntry, for customizations outside the Tar tasks basic capabilities. This would also be useful as a workaround for the inability to create empty folders in tars.

Comment by Ioan Eugen Stan [ 04/Mar/16 ]

This should be possible in Java 7 using the new API: https://docs.oracle.com/javase/7/docs/api/java/nio/file/attribute/PosixFileAttributeView.html

Any ETA on gradle requiring minimum Java 7?

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 11:54:18 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.