-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Eliminate Gradle task input warnings #47538
Eliminate Gradle task input warnings #47538
Conversation
Signed-off-by: Mark Vieira <[email protected]>
Signed-off-by: Mark Vieira <[email protected]>
Pinging @elastic/es-core-infra (:Core/Infra/Build) |
Signed-off-by: Mark Vieira <[email protected]>
Signed-off-by: Mark Vieira <[email protected]>
Signed-off-by: Mark Vieira <[email protected]>
Signed-off-by: Mark Vieira <[email protected]>
@elasticmachine update branch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for taking this on! These warnings have been an eyesore for far too long. LGTM
@elasticmachine run elasticsearch-ci/docs |
@@ -49,11 +50,16 @@ public Chmod getChmod() { | |||
throw new UnsupportedOperationException(); | |||
} | |||
|
|||
@Input | |||
@Internal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm assuming a non existing File
can't be input ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue here was Gradle was complaining that we were using @Input
for File
when we should have been using @InputFile
or @InputDirectory
. Using @Input
tracks the File
path, not it's contents, which is actually the behavior we want, but Gradle is issuing a warning here because we aren't being explicit. That's why I've added the input for the directory path, which is all we care about.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM Thanks allot for this !
(cherry picked from commit e86d40f)
We have a number of tasks that either omit, or incorrectly apply Gradle input/output annotations on task properties. In addition to some of these instances resulting in potentially incorrect incremental build behavior, this causes a bunch of noise whenever we build
:buildSrc
. This PR addresses these reported warnings.