Ok I guess that means people should pay more attention to the change notes when upgrading the android plugin.
http://tools.android.com/tech-docs/new-build-system - *BREAKING CHANGES*: - DSL for Library Projects is now the same as for application projects. - You can create/configure more build types, in the buildTypes { ... } container. - You can create product flavors using the productFlavors { ... } container. - You can create signingConfigs using the signingConfigs { ... } container. - instrumentTest was renamed androidTest It would have been nice though if the migration wizard would have pointed this out. On Saturday, March 8, 2014 7:33:02 AM UTC+1, Rainer Burgstaller wrote: > > Hi > > I don't know for sure whether this was also the case in 0.5.0 but it > definitely worked fine in 0.4.6. So I have a project with unit tests in > src/instrumentTest/java. > > If I hit CMD-T on a normal class and choose Create Test ... then it asks > me whether I want to create the test in the same source folder. If I choose > no then I get a path selection dialog that does not include any of the > instrumentTest source folders. > Upon further inspection it shows that all unit tests seem to have a red > "J" icon in the project explorer. When I choose a directory of one of the > tests and enter CMD-N to manually create a new java class, I don't get the > option for "Java Class" but only things like File Directory (see > screenshots). > > Please help! > -- 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.
