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.
