I see this in Find in Path as well. When I use that feature, I immediately have to collapse all the build directories in order to get to the real results. Big pain.
This on Android Studio 0.5.3 with a basic Android project structure. On Tuesday, November 19, 2013 4:19:40 PM UTC-5, Adam Brown wrote: > > Sorry I meant the open file dialog, so (using the Eclipse shortcut > binding) I do Ctrl + Shift + R, begin type the class name to open it's > file, and both the .java and .class files come up in the results. > > Also, it's just kind of nice to only see the things we are actually > interested in in the project browser: src, res, assets, ect. > > > On Tue, Nov 19, 2013 at 12:05 PM, Scott Barta <[email protected]<javascript:> > > wrote: > >> Find Symbol isn't searching build/ for me. Can you file a bug with a >> reproducible case? >> >> One of our goals in removing the option is to understand what folks were >> using it for, and if it's to work around bugs, we'd much prefer to just fix >> the bugs. >> >> >> On Tue, Nov 19, 2013 at 11:57 AM, Adam Brown <[email protected]<javascript:> >> > wrote: >> >>> Ah ya this is a pain. Without the exclude option, things like the find >>> symbol function also search in the build/ dir and you get results from >>> .class files. We really need a way to hide & ignore bin & build. >>> >>> >>> On Saturday, November 9, 2013 5:02:30 AM UTC-8, David Laurell wrote: >>>> >>>> Hi, >>>> >>>> Up until now we could mark different directories as test source root so >>>> we would get auto complete stuff in junit test classes. Now this option >>>> seems to have disappeared. >>>> >>>> I'm using the gradle-android-test-plugin to write unit tests with >>>> Robolectric. The tests are put in src/main/test and we could do the >>>> following hack to get Android Studio to resolve the dependencies in the >>>> test classes: >>>> >>>> testCompile 'junit:junit:4.10' >>>> testCompile 'org.robolectric:robolectric:2.1.+' >>>> testCompile 'com.squareup:fest-android:1.0.+' >>>> >>>> //Used for Android Studio so it finds the references >>>> instrumentTestCompile 'junit:junit:4.10' >>>> instrumentTestCompile 'org.robolectric:robolectric:2.1.+' >>>> instrumentTestCompile 'com.squareup:fest-android:1.0.+' >>>> >>>> I would rather that Android Studio could resolve the testCompile >>>> dependencies and mark junit directories as test source roots too. Then we >>>> can have both instrumentTests on a device and running local junit tests >>>> out >>>> of the box! >>>> >>>> Anyone have any solutions for this? >>>> >>> -- >>> 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] <javascript:>. >>> >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- >> 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/v0AluPBcoy0/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- 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.
