Use Gradle filesystem types for task properties #2707
Merged
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.
part of #2700
Using Gradle filesystem types allows for more idiomatic usage of Gradle, and makes it easier to wire task inputs and outputs together.
I changed these properties to be managed types, as they are easier to create.
I also started moving some of the conventional values for these properties into DokkaPlugin. I intend to move more of this property convention into DokkaPlugin, as this makes it easier to re-use properties and values, and wire tasks together. When the conventions are set inside a Task, they are limited by what they can access from the
project
instance, which can make for repetitive or tough to follow code.This PR includes changes from