refactor: improve the tck process to be lazy evaluated #2069
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was speaking to https://github.com/vampire in the Gradle slack and he had some feedback on my original tck implementation. I think I implemented them the way he suggested so they're lazy and the task does not occur at configuration time.
Some highlights of that conversation:
copy { ... }orsync { ... }in adoFirstordoLastblock.resolve()is 99.87% of the time the wrong solution.Copyorcopy { ... }should almost 98.7% of the time beSyncorsync { ... }to not risk leaving stale files lying around.@matrei with this new found education from an amazing developer, I thought I'd improve my original implementation =)