Force IntelliJ Analysis

[Michael Wallstedt]

If I have a compilation error in my project, there seems to be two ways to learn about it in Android Studio: from gradle, and from the IDE itself. All of the obvious options (e.g. Make Project, Make Module, Rebuild Project) appear to invoke gradle. If I want IntelliJ to recognize these errors without any help from gradle, it's possible for a single file, providing that I open it explicitly. For the lack of a better term, I'll refer to this as "analysis", since IntelliJ need not generate a .class file to find the errors. My question is: Is there a way of forcing this analysis on an entire module in Android Studio?

[Tor Norbye]

Do you mean something other than Analyze > Inspect Code... and then choosing the module as the scope?

-- Tor

On Thu, Sep 25, 2014 at 4:51 PM, Michael Wallstedt <mikewa...@google.com> wrote:

If I have a compilation error in my project, there seems to be two ways to learn about it in Android Studio: from gradle, and from the IDE itself. All of the obvious options (e.g. Make Project, Make Module, Rebuild Project) appear to invoke gradle. If I want IntelliJ to recognize these errors without any help from gradle, it's possible for a single file, providing that I open it explicitly. For the lack of a better term, I'll refer to this as "analysis", since IntelliJ need not generate a .class file to find the errors. My question is: Is there a way of forcing this analysis on an entire module in Android Studio?

--
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 adt-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael Wallstedt]

While useful, I don't think that meets our needs. My concerns are that it is a bit slow, and that it produces far more information to sift through than we want.

In our current project, changes to the application code may cause compilation errors in the test code which are not easily surfaced. In Eclipse, the errors would be highlighted immediately. In Android Studio, we aren't even able to invoke Make Module on the test module, due to another issue (https://groups.google.com/forum/#!topic/adt-dev/ORu_0EZ0BWI). Having encouraged some of our team members to drop Eclipse, I'd really like to fix what is perceived as a regression in behavior.

--
You received this message because you are subscribed to a topic in the Google Groups "adt-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/adt-dev/Z_lOcSrn26Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to adt-dev+u...@googlegroups.com.