-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix task execution for certain configurations #1
base: develop
Are you sure you want to change the base?
Conversation
08f5793
to
f425a3e
Compare
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, but I'd remove all changes except the fix itself before opening a PR against upstream.
} | ||
project.tasks.getByName("check").dependsOn(apiCheck) | ||
} | ||
|
||
// the task handed to isSatisfiedBy is never used, so it does not matter what we hand over. |
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 think passing this
is actually the correct task. The gradle api is old java code, so this is intended to be some class in some other file, hence they pass the Task
into the callback. with kotlin you almost never need it, because if used with a lambda, you capture it anyways. TL/DR: I'd just remove that comment.
2bf8b7f
to
02527d0
Compare
02527d0
to
d8d7331
Compare
whether tasks should be executed. This fixes a bug where tasks would not be executed, because srcDirs would not yet exist at configuration time.
d8d7331
to
cb69686
Compare
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!
There is not JIRA page yet to document the issues.