-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GRADLE-796/673 Preserving permissions by default in copy/archive tasks #62
Conversation
…ymlinkIntegrationTest.
…replicating the changes made to FileCollectionSymlinkIntegrationTest).
…he file. Implemented for regular files & archives.
Permissions are now preserved by default. They can still be set using fileMode/dirMode and can also be set on individual files using copy actions. FileCopySpecVisitor now honors file modes (implicitly through AbstractFileTreeElement.copyTo(..)) The actual permissions that will be used for any given file are exposed to copy actions. The actions can also set permissions using the new FileCopyDetails.setMode().
…eserved by default. Everything related to permissions during copying is covered in unit-test + CopyTaskPermissionsIntegrationTest.
…ew, nullable fileMode/dirMode. Updating the DSL docs with the new default values (null) for fileMode/dirMode.
This looks good. We're just working on getting 1.0-milestone-8 out of the door, so we'll apply the patch after milestone 8 is out. |
Ok good.. Found another issue that is fixed as well after this is merged... GRADLE-971 |
Conflicts: subprojects/core/src/main/groovy/org/gradle/api/file/CopyProcessingSpec.java
I just tried to resolve a conflict in CopyProcessingSpec. It's the first time I've done this with git, not sure if I was supposed to add those merge commits to the pull request.. |
Sweet.. GRADLE-971 can be closed as well.. |
Thanks for fixing this! |
Implemented changes as discussed on the mailing list.