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

Provide method to get relative file path from InputFileDetails #731

Closed
eriwen opened this issue Oct 19, 2016 · 3 comments
Closed

Provide method to get relative file path from InputFileDetails #731

eriwen opened this issue Oct 19, 2016 · 3 comments
Labels
a:feature A new functionality stale

Comments

@eriwen
Copy link
Contributor

eriwen commented Oct 19, 2016

Plugin authors like myself need incremental tasks that preserves source directory structure in the output.

For example:

Input

style.css
vendor/bootstrap.css

Output

$buildDir/style.min.css
$buildDir/vendor/bootstrap.min.css

I would like this test to pass using IncrementalTaskInputs. See here also.

@eriwen eriwen added the a:feature A new functionality label Oct 19, 2016
@adammurdoch
Copy link
Member

I would add methods to ask for filtered FileCollection and FileTree instances, that contain the changed/added/removed input files. This way, I can use the same APIs to iterate over the input for both incremental and non-incremental execution.

I would avoid just adding more stuff to InputFileDetails.

@stale
Copy link

stale bot commented Jun 9, 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 how we try to keep the backlog in a healthy state, please read our blog post on how we groom 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 Jun 9, 2020
@stale
Copy link

stale bot commented Jun 30, 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 Jun 30, 2020
@wolfs wolfs closed this as not planned Won't fix, can't repro, duplicate, stale Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:feature A new functionality stale
Projects
None yet
Development

No branches or pull requests

3 participants