Fixed
Status Update
Comments
tn...@google.com <tn...@google.com> #2
can you share sample project to reproduce same issue.
sp...@google.com <sp...@google.com> #3
It happens in our company's real project and I am not able to share it.
It contains a Java module, 3 different Android module which one of them contains C/C++ native library that is being built by Cmake.
It is a BLE project with 100% kotlin code base by using latest Android build tools.
It contains a Java module, 3 different Android module which one of them contains C/C++ native library that is being built by Cmake.
It is a BLE project with 100% kotlin code base by using latest Android build tools.
sp...@google.com <sp...@google.com> #4
One more update, today I updated to Canary 8 and problem still remains. Canary 4 is the lastest version that is working fine.
[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 :)