Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
[ID: 558956]
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
Currently, with
android.lintOptions.textReport true
, lint will output results to stdout when theAndroidLintTask
(e.g.,lintDebug
) runs, but there will be no such output if the task is up-to-date, which might mislead users to think that there are no lint issues.The desired behavior is for lint to output issues to stdout even if the task is up-to-date (or not to output anything if there are no issues - see Issue 158259845 ).
A possible fix would be to add a new lightweight task which would never be up-to-date and would only print the text report. I.e., change the lint build flow from this:
lintAnalyzeDebug
->lintDebug
to this:
lintAnalyzeDebug
->lintReportDebug
->lintDebug
where the new
lintReportDebug
task is the oldlintDebug
task, and the newlintDebug
is the lightweight task that is never up-to-date.Rejected alternative:
I considered modifying Issue 189877657
AndroidLintCopyReportTask
to print out the text report, but that task will not run ifAndroidLintTask
is up-to-date. In fact, we can consider adding that task's functionality to the new lightweight lint task to properly fixPS - Thanks to Tor for noticing this issue :)