chore(gradle): jarFileTest setup #9582
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was simply a call to project.file which has no effect on this task. The inputs prefix was not added when this was added with commit: b5331f4
When using gradle types as inputs task dependencies are tracked automatically. task.outputs returns a gradle type while singleFile returns a plain java File.
This is the new and recommended way and also how it is done for the unit-test setup internally in gradle by now.
|
Hi, thanks for the PR. The plugin is still incubating. |
|
Yeah sure, but there is tons of people already relying on it, also gradle interally, so I bet any changes will be minor. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The commit descriptions should be self explanatory.
For the JvmTestSuitePlugin docs see here.