IntelliJ does things differently when it comes to importing Gradle project (even though our support is based on theirs). Either use Studio or talk to JetBrains.
On Wed, May 6, 2015 at 12:14 AM, Super Nova <[email protected]> wrote: > IntelliJ Idea 14.1.2 I am still having the same issue.. > > > On Friday, 13 June 2014 16:37:01 UTC+8, Jelle Nagels wrote: >> >> This has been fixed. I just received the update! Thanks! >> >> Op woensdag 11 juni 2014 18:33:46 UTC+2 schreef Nicholas Campion: >>> >>> Thanks for the quick fix. We're seeing this same error and its now >>> disrupting our development. When can we expect the weekly release? >>> >>> On Tuesday, June 10, 2014 10:55:42 PM UTC-5, Alex Ruiz wrote: >>>> >>>> A fix will be included in this week's release: >>>> https://android-review.googlesource.com/97446 . Sorry for the trouble! >>>> >>>> >>>> On Tue, Jun 10, 2014 at 7:16 AM, Kyle Fowler <[email protected]> >>>> wrote: >>>> >>>>> This sounds close to what I'm experiencing but I also have the issue >>>>> with projects only 1 level deep. The issue is not consistent between our >>>>> dev team, a bunch of people have different versions of the issue effecting >>>>> all levels of build.gradle nesting. My issue looks like the one below >>>>> where >>>>> appone and libone are recognized by AS but apptwo is not. >>>>> >>>>> | Project >>>>> | build.gradle >>>>> | settings.gradle >>>>> | appone >>>>> | build.gradle >>>>> | apptwo >>>>> | build.gradle >>>>> | libs >>>>> | libone >>>>> | build.gradle >>>>> >>>>> On Tuesday, June 10, 2014 4:03:32 AM UTC-7, Alex Ruiz wrote: >>>>> >>>>>> There is a ticket that Studio cannot see gradle modules in >>>>>> subdirectories more than 1 level deep: https://code.google.com/p/ >>>>>> android/issues/detail?id=71098 . >>>>>> >>>>>> Jake, the output you provided seems to confirm this is the bug you >>>>>> are experiencing. >>>>>> >>>>>> Kyle, can you please confirm this as well? >>>>>> >>>>>> This is really strange behavior, since this area of the code hasn't >>>>>> been changed. I'm working on a fix. >>>>>> >>>>>> Thanks! >>>>>> -Alex >>>>>> >>>>>> >>>>>> On Mon, Jun 9, 2014 at 7:34 PM, Jake Wharton <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Seeing something like this as well. When I force sync: >>>>>>> >>>>>>> Failed to set up dependencies >>>>>>> Warning:Unable to find module with Gradle path >>>>>>> ':common:foo:foo-android'. Linking to library 'foo-android' instead. >>>>>>> Warning:Unable to find module with Gradle path ':common:bar'. Linking >>>>>>> to library 'bar' instead. >>>>>>> Error:Unable to find module with Gradle path >>>>>>> ':common:foo:foo-annotations'. >>>>>>> Warning:Unable to find module with Gradle path ':common:baz'. Linking >>>>>>> to library 'baz' instead. >>>>>>> Error:Unable to find module with Gradle path ':hey:hey-protos'. >>>>>>> Warning:Unable to find module with Gradle path ':common:baz'. Linking >>>>>>> to library 'baz' instead. >>>>>>> Warning:Unable to find module with Gradle path ':common:bar'. Linking >>>>>>> to library 'bar' instead. >>>>>>> Error:Unable to find module with Gradle path ':hi:hi-protos'. >>>>>>> Error:Unable to find module with Gradle path >>>>>>> ':common:foo:foo-annotations'. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Mon, Jun 9, 2014 at 7:11 PM, Kyle Fowler <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> After this last update, the IDE decides to not pickup one/many of >>>>>>>> the projects in settings.gradle as modules for the project. For me >>>>>>>> this is >>>>>>>> only happening to 1 of the 8 modules for me but 5/8 for a coworker. >>>>>>>> When >>>>>>>> going to open one of the build.gradle files for a project that has been >>>>>>>> missed, AS gives me the nice warning that it thinks it isnt included ( >>>>>>>> http://cl.ly/image/3q1N18470f15). Clicking on the "add now" >>>>>>>> action, I get presented with the new module dialog but when I try to >>>>>>>> add >>>>>>>> this module it says "Project already contains module with this name", >>>>>>>> which >>>>>>>> is correct, it does. So why doesn't AS pick this up as a module where >>>>>>>> it >>>>>>>> really matters? Is this a known issue? I havent seen anything about >>>>>>>> similar >>>>>>>> behavior. >>>>>>>> >>>>>>>> All of the build.gradle files in the project user buildTools 19.1 >>>>>>>> and the project has a gradle version of 1.11. Building via gradle from >>>>>>>> the >>>>>>>> CLI works just fine, only thing having issues is AS. >>>>>>>> >>>>>>>> Any ideas would be really appreciated! Thanks. >>>>>>>> >>>>>>>> -- >>>>>>>> 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. >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> 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. >>>>>>> >>>>>> >>>>>> -- >>>>> 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. >>>>> >>>> >>>> -- > 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. > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. http://developer.android.com | http://tools.android.com Please do not send me questions directly. Thanks! -- 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.
