Difference between running lint via Android Studio menu and gradlew command-line

android gradle android-studio lint gradlew
gonzobrains picture gonzobrains · Jul 22, 2014 · Viewed 9k times · Source

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?

Answer

Robert picture Robert · Nov 11, 2015

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

Related questions

Android Studio lint reports "cannot infer argument types."

I have reviewed the Inspection report for my project that is provided by Android Studio after having executed the following command: Analyze->Inspect Code... The report indicates a problem with this code snippet in my gradle.build file: buildTypes { …

Read More
How to update gradle in android studio?

I installed Android Studio 0.1.9. Today I got and update to version 0.2 and of course I updated. After the installation I restarted Android Studio but now I get this message: Project is using an old version of the Android Gradle plug-in. …

Read More
Error retrieving parent for item: No resource found that matches the given name after upgrading to AppCompat v23

I've always programmed Android with Eclipse and decided to start migrating to Android Studio. I decided to use the same SDK I already had for Eclipse, then: Started a new project Set minimum SDK 4.0 (API Level 14) Choose Blank Activity option …

Read More