The "detektCheck" Gradle task is never UP-TO-DATE #725
Labels
Milestone
Comments
|
The main drawback is that right now it's not incremental which it should be. |
|
So how to change that? Any gradle experts here :) |
|
We need to declare an input. Probably the source files. Gradle will then do the rest of the work. |
|
The tasks should have both inputs and outputs. |
|
Right as output we could use our output. |
|
I can take a pass at the Gradle stuff sometime next week after #719 is completed |
sschuberth
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Mar 19, 2018
This version as the UP-TO-DATE check fixed, see detekt/detekt#725 Also, the "warningThreshold" and 'failThreshold' properties were deprecated in favor of the new "maxIssues" property, see detekt/detekt#313
sschuberth
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Mar 20, 2018
This version as the UP-TO-DATE check fixed, see detekt/detekt#725 Also, the "warningThreshold" and "failThreshold" properties were deprecated in favor of the new "maxIssues" property, see detekt/detekt#313
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related topics. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I just realized that running the exact same
./gradlew detektChecktask two times in a row without changing any source code does not show thedetektChecktask to beUP-TO-DATE, as expected, but runs the task again. Is that by design? If so, I'd vote for changing that for performance reasons, and because tasks can be easily forced to rerun with the--rerun-tasksGradle command line option.The text was updated successfully, but these errors were encountered: