Alex, Still doesn't work for me.
When you say you've verified it, are you talking about a 1.2.0-beta3 of gradle plugin? Or Android Studio 1.2b3? I'm using Android Studio 1.2 RC and Gradle plugin 1.2.0-beta2 To repro, you just import an AAR using the Android Studio "New Module" GUI. For us, it's Urban Airship's Android SDK, which comes as an AAR. http://docs.urbanairship.com/platform/android.html#add-the-library-to-your-project While the gradle build is fine, the Android Studio editor UI shows the referenced classes as unresolvable. Classes unresolvable: https://www.dropbox.com/s/ozk13hs45i7r1az/Screenshot%202015-04-22%2013.36.53.png?dl=0 build.gradle generated for AAR: https://www.dropbox.com/s/g849y2tndtk54qa/Screenshot%202015-04-22%2013.40.15.png?dl=0 Hope this helps. Kevin On Mon, Apr 20, 2015 at 8:46 PM 'Alex Ruiz' via adt-dev < [email protected]> wrote: > Kevin, I verified that the bug is fixed in 1.2.0 beta 3, please give this > version a try. If you can still experience the issue, please provide steps > to reproduce and I'll look at it right away. > > Thanks. > > On Mon, Apr 20, 2015 at 2:17 PM, Kevin Lim <[email protected]> wrote: > >> Issue still happens on gradle plugin 1.2.0-beta2 >> >> >> On Monday, April 6, 2015 at 2:17:23 PM UTC-5, Kevin Lim wrote: >>> >>> I am seeing this too, specifically with the urbanairship SDK (imported >>> using aar wrapper project). >>> >>> Here's the bug in Google's tracker, currently assigned to Tor: >>> https://code.google.com/p/android/issues/detail?id=162634 >>> >>> Staying on 1.0.x gradle plugin is workaround for me. >>> >>> >>> On Wednesday, April 1, 2015 at 12:38:54 PM UTC-7, Adrian Opyrchał wrote: >>>> >>>> For now use gradle build tools 1.0.1 >>>> classpath 'com.android.tools.build:gradle:1.0.1' in project >>>> build.gradle >>>> >>>> Add jar or aar package from File -> New Module -> Import jar/aar >>>> >>>> Dont forget to add imported module to your build.gradle as dependency >>>> >>>> dependencies { >>>> .... >>>> compile project(':NameOfImportedModule') >>>> .... >>>> } >>>> >>>> >>>> >>>> W dniu środa, 1 kwietnia 2015 19:19:15 UTC+2 użytkownik Cody Mace >>>> napisał: >>>>> >>>>> The canary channel doesn't seem to fix this issue for me either. Does >>>>> anybody know of a temporary solution if not a good solid one? I really to >>>>> get this working because I need to finish up a project that is full of >>>>> library dependencies. >>>>> >>>>> On Monday, March 16, 2015 at 2:45:48 PM UTC-6, Greg Macdonald wrote: >>>>>> >>>>>> We have external jar and aar libraries added to our project using >>>>>> this technique: >>>>>> 1. In AS do New Module and select Import .JAR or .AAR Package >>>>>> This creates project folder with a simple build.gradle, >>>>>> proj_name.iml and the jar or aar file >>>>>> 2. In dependent module's module dependencies setting, add Module >>>>>> dependency >>>>>> i.e. compile project(':proj_name') >>>>>> >>>>>> This works fine thru plugin 1.0.1, but if I change to 1.1.0 or later, >>>>>> then I get 'cannot resolve symbol' errors in the editor. The imports are >>>>>> resolved and the project builds and runs, but, since the AS ide is >>>>>> confused, all symbols from the library show red with the cannot resolve >>>>>> error, and both code completion and the ability to follow a symbol >>>>>> (cmd-click) are broken. >>>>>> >>>>>> In the case where the lib is a jar, I find I can resolve this by >>>>>> adding to the dependent libr's gradle file: >>>>>> dependencies { >>>>>> compile fileTree(dir: '../proj_name_dir', include: ['*.jar']) >>>>>> } >>>>>> >>>>>> Which surely seems a hack, and it doesn't work for aar files. >>>>>> >>>>>> In the release notes for 1.1.0 comments under "Fixes and changes to >>>>>> the dependency management", there are comments about how >>>>>> dependencies have been made correct. Are there some notes somewhere on >>>>>> what correct looks like and how I should be doing dependencies on these >>>>>> external libs? >>>>>> >>>>>> thanks, >>>>>> greg >>>>>> >>>>> -- >> 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 a topic in the > Google Groups "adt-dev" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/adt-dev/1Ho_c8dALQQ/unsubscribe. > To unsubscribe from this group and all its topics, 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.
