I really think that gradle sync mechanism should be more fail proof and not depend on project compilation. I'm often in situation when we want to switch to newer od different dependency which is not source compatible. It looks easy, you just change the dependency in the gradle, build the project and IDE itself mark all errors (invalid imports, missing method arguments, etc) itself. So you just fix the red lines. It works in normal Java world with maven. But not with Android Studio and Gradle. Because gradle sync fail because of compilation error and AS will not add new dependency on the IDE classpath and you can't use it. Why setup IDE dependencies depend on the project compilation? All gradle script are fine and there is not error during build configuration setup. It should resolve all dependencies from the gradle files and update IDE classpath for code completion and error checking and then start with the compilation itself. Now it looks that IDE classpath is updated at the end of the sync process after compilation :-( You mentioned on the last Google IO that 2.2 has new gradle sync handling, so I hoped that this will be fixed too :-(
-- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
