Lint checks run on modules that don't have Timber dependency
See original GitHub issueLet’s say we have: module A - doesn’t depend on Timber. Uses android.util.Log for logging. module B - depends on A and Timber
Now if we run lint like ./gradlew lint the Timber’s lint checks will also run on module A and will produce a violation of LogNotTimber check.
I’m not sure if this is a Timber bug or AGP bug.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Android Studio 3.6 is not performing lint checks from modules
1. Open the Timber project. · 2. Open `LintActivity` in the timber-sample module. · 3. Uncheck all the suppressions. · 4. From the...
Read more >Android Lint API Guide - Google Samples
The implementation of the lint check which registers Issues, analyzes the code, and reports Incidents. An Implementation tells lint how a given issue...
Read more >Writing custom lint checks in Android | by Parth Gupta - Medium
Writing custom lint rule. We need to create a new module(java/kotlin library) and add all required dependencies as compileOnly as this module ......
Read more >Android Studio Lint check for Unnecessary Module Dependency
This inspection lists modules which contain redundant dependencies on other modules. These dependencies can be safely removed. intellij-idea · android-studio ...
Read more >Managing Logging in a Multi-Module Android Application
Additional we have around 5 in-house libraries/dependencies we use and of ... And two, it supports a lot of very convenient lint checks....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

This Android Studio issue (see also: #149) also arises when using multiple-instance Android Studio, with project A having Timber and project B not, then lint will issue warnings in project B as well. Edit : clarification of phrasing
@jrodbx I’ve filled https://issuetracker.google.com/issues/69394971
./gradlew :A:lintoutputs the same violation with 3.0.0 but with 3.1.0-alpha03 it now works correctly.