Fixed
Status Update
Comments
tn...@google.com <tn...@google.com> #2
That seems like a big limitation because it means that to get lint checks on them you need to add them to the base but then they are also packaged with the base instead of the dynamic-features. Can we attempt to fix this for 7.1?
sp...@google.com <sp...@google.com> #3
Ok, yes, I can attempt to fix for 7.1.
[Deleted User] <[Deleted User]> #5
Comment has been deleted.
ru...@gmail.com <ru...@gmail.com> #6
Comment has been deleted.
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 :)