When I run the following on a command line:
./gradlew -lint
I get different results than if I choose the following menu option within Android Studio.
Analyze->Inspect Code...
Can anyone explain this? Is this normal? Should a prudent developer run both in order to find all potential problems with his/her project?
The lint tool checks your Android project source files for potential bugs and optimization improvements for correctness, security, performance, usability, accessibility, and internationalization.
You can execute all the build tasks available to your Android project using the Gradle wrapper command line tool. It's available as a batch file for Windows ( gradlew. bat ) and a shell script for Linux and Mac ( gradlew.sh ), and it's accessible from the root of each project you create with Android Studio.
Lint, or a linter, is a static code analysis tool used to flag programming errors, bugs, stylistic errors and suspicious constructs. The term originates from a Unix utility that examined C language source code.
You are running two different tools. The command:
$ ./gradlew lint
runs the lint tool that comes with the Android SDK and the menu option
Analyze->Inspect Code...
in Android Studio is a feature inherited from JetBrains IntelliJ IDEA which runs:
<android studio path>/bin/inspect.sh
In Android Studio you can customize what inspections are run via Preferences > Inspections; you may have some Lint inspections disabled, and not all run by default. Android Studio can also run a great number of non-Lint inspections.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With