On Thu, Mar 13, 2014 at 4:03 AM, Mike Kulasinski < [email protected]> wrote:
> Hey > > Can you please confirm if Android studio does use the same lint > configuration as gradle? When I run Inspect on Android Studio I have > different errors than when I run it from command line by gradle. I have > gradle 1.11 and Android Plugin 0.9 > > Also InvalidPackage error is only shout when I run the lint check from > command line but not being shout when it is run from Android Studio. > > We are aiming to have the same output of lint on developer machine as on > our continuous integration server. > I can confirm that they are *not* the same, though not deliberately so. When lint is run inside IntelliJ and Android Studio, it does not run any of the bytecode-based lint checks (and the invalid package error is one of those). They don't work for two reasons: (1) there may not be any bytecode yet, if the project has not been built (or the bytecode may be out of date w.r.t. the source files) since IntelliJ does not do compile-on-save; building is an explicit user action. (2) lint's bytecode analysis uses ASM4, and it runs into class loading issues because of an incompatible version already used in IntelliJ Both issues are fixable, and are on my radar. -- Tor -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
