Skip to content
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

Allow a zipTree or tarTree to be created from the output of a task #10072

Open
adammurdoch opened this issue Jul 24, 2019 · 3 comments
Open

Allow a zipTree or tarTree to be created from the output of a task #10072

adammurdoch opened this issue Jul 24, 2019 · 3 comments
Labels
a:feature A new functionality in:configuration-model lazy api, domain object container in:provider-api property lazy provider MapProperty ListProperty DirectoryProperty

Comments

@adammurdoch
Copy link
Member

The zipTree() and tarTree() methods discard any details about the tasks that produce the archive, making it very difficult to create a tree from an archive that is built by a task.

Expected Behavior

Provide an easy way to take a zip or tar archive produced by a task, represented as a Provider, and map it to a FileTree that honors the producing task information. Ideally, querying the contents of the tree would fail with a nice message if the task has not yet completed in this build.

Current Behavior

The FileTree discard producer task information.

Context

@adammurdoch adammurdoch added a:feature A new functionality from:contributor in:configuration-model lazy api, domain object container labels Jul 24, 2019
@stale
Copy link

stale bot commented Oct 6, 2020

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

@stale stale bot added the stale label Oct 6, 2020
@stale
Copy link

stale bot commented Oct 28, 2020

This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to reopen the issue with steps to reproduce, a quick explanation of your use case or a high-quality pull request.

@stale stale bot closed this as completed Oct 28, 2020
@wolfs wolfs closed this as not planned Won't fix, can't repro, duplicate, stale Sep 16, 2022
@ov7a ov7a added in:provider-api property lazy provider MapProperty ListProperty DirectoryProperty to-triage and removed stale labels Sep 21, 2023
@ov7a ov7a reopened this Sep 21, 2023
@jbartok
Copy link
Member

jbartok commented Sep 22, 2023

Thank you for your interest in Gradle!

This feature request is in the backlog of the relevant team, but this area of Gradle is currently not in focus. It might take a while before it gets implemented.

@jbartok jbartok added in:configuration-model lazy api, domain object container and removed in:configuration-model lazy api, domain object container to-triage labels Sep 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:feature A new functionality in:configuration-model lazy api, domain object container in:provider-api property lazy provider MapProperty ListProperty DirectoryProperty
Projects
None yet
Development

No branches or pull requests

4 participants