Shared publicly  - 
The #android plugin for #gradle has been updated to version 0.4.2 with the following changes:

- Fixed incremental support for resource merging.
- Fixed issue where all pngs would be processed in parallel with no limit on the number of thread used, leading to failure to run aapt.
- Fixed ignoreAsset support in aaptOptions
- Added more logging on failure to merge manifests.
- Added flavor names to the TestServer API.

Additionally we have released 2 new SDK components: Android Support Repository, and Google Repository. These components are Maven repositories and the Gradle plugin automatically add them to your list of repositories. They gives you access to the following artifacts:


Using these artifacts in your build will greatly reduce problems, particularly when you have more than one Library Project that needs support-v4. Gradle will automatically detect similar artifacts and select only one (detecting version conflicts if they exists).

We have updated the Play Services samples to use Gradle and these artifacts. They are available here:

Make sure to download these two repositories through the Android SDK Manager.
Ken Yee's profile photoThomas Handler's profile photoLuis E. Fernandez's profile photoOscar Sommerer's profile photo
Good news but the mirrors don't seem to have it yet. Waiting...
Just a silly question: Why set up two maven repositories and not pushing the artifacts to maven central? Since maven central forbids third party repositories in pom.xml it would not be possible to push libraries that use them to maven central. (Think of actionbarsherlock for example)
To install these, open SDK Manager and install the Android Support Repository and Google Repository. They will not be on Maven Central as they require you to explicitly accept a click through license.
+David Kunzler I guess this is due to the fact that getting stuff into the maven central repository usually takes time. I'm pretty sure the request to push these artifacts to maven central was already filed. Using these two repositories allow +Android Developers to get the libs to us as fast as possible.

Also see +Xavier Ducrohet s comment regarding the license on +Tor Norbye s reshare.
I had a look at the new Android Support Repository. After installing with the SDK manager, it goes to <android-sdk>/extras/android/m2repository. It's including the latest version of the support library in its v4 and v13 flavours as well as the gridlayout library. The artifacts are contained including their source and a .pom file. However, building will not be straightforward because the .pom file is missing dependencies and build instructions. It's just a naked artifact declaration.

In order to get the artifacts to Maven central, we still need to find a way to build an Android API artifact that can be linked to when compiling. That appears to remain the hard part. As far as I can tell, Google did not change anything regarding this hurdle.
Re: gpsdemos - Do the new repositories need to be specified in the project's build.gradle? Only mavenCentral in there right now.  README for the plus sample still says you need to manually add the support library, and the plus demo does not build out of the box in Android Studio, in fact complaining about the missing support lib.
How are these samples intended to be used?  A bit more instruction in the READMe would be very helpful.
+Brad Armstrong Open your SDK manager and scroll down to "Extras". In there you will see two new items: "Android Support Repository" and "Google Repository". Once you install those you will be able to reference the new libraries from gradle
Cool! Here's hoping that other stuff, like Volley, will soon be available in repos too.
+Artiom Chilaru Thanks for the reply.  Should have mentioned that I did have the new repos installed.  I read the announcement a bit closer and it appears the android plugin manages those repo dependencies for you. The sample projects work fine when build using gradlew but the library dependencies do not resolve when trying to work with it in Android Studio.  
+Brad Armstrong no idea why you're having these issues.. I've been working with it for the last couple days, and it worked quite well for me :)
Builds fine on the command line, if I add Play Services as a dependency in the gradle config, but Android Studio still doesn't know all the classes and shows them as errors. Any hints?
Did you try that synchronize button in the right part of the icon buttons? I think you need to press it after changing dependencies in the gradle file.
Wouldn't that also be cured by restarting Android Studio?
can't get the new SDK components - support and android maven repository via android update command line.
such as 'android update sdk --filter extra -u' or 'android update sdk', any suggestion? 
Not sure what else to try... I just ran all possible updates to the SDK, downloaded and tried to open the Maps project into Android Studio but no luck. First, it shows an error for
And also can't find R, like R.layout... and all references to R.
Can somebody list the steps to run the maps demo into android studio.
Thank you +Android Developers 
What about GCM? Shouldn't be in some kind of repository too?
+Ricardo Amaral It's all in one now. The idea is that your users just need to update play services to get all new features. 
Just tried this. ran ./gradlew installDebug and it built, installed, in ran but the maps are blank. Any ideas what could be wrong. Do I have to setup the Map Key or something?  -- YES: Answered my own question by Importing the project to Android Studio and reading the comment above the <meta-data> in the AndroidManafest.xml under the maps Module
Sadly none of the solutions provided so far work anymore.. '' fails to resolve in the latest Android Studio (but works in terminal with gradlew).
I double and triple checked to use the same SDK for both and I don't have the ANDROID_HOME env but rather for both.
Could it be a problem with AS not resolving .aar's correctly? I noticed android-suppor is still a .jar while play-services uses aar archives. 

[EDIT - solved] apparently it's vital to add '.aar' to the registered archive types in Android Studio settings. Why isn't this by default?
+Android Developers can we have some documentation/intro to the new build system? And the Android Studio?

Not only the build system has changed, but the IDE too! too many changes! :)
Hi, how can I use this with the 'old' Eclipse + Maven, in the pom file of my project?
Kun Li
How do we know the version number is updated? For example, I'm using now, but how do I know if 3.1.37 or 3.2 is released?
I get this here after adding the google play services to compile('')
Gradle: A problem occurred configuring project ':LocationDemos'.
> Failed to notify project evaluation listener.
   > Could not resolve all dependencies for configuration ':LocationDemos:_DebugCompile'.
      > Could not find
        Required by:
play-services:3.1.36 ? Can't find  net.gcm package…
Everyone with missing play-services in AndroidStudio - please make sure you've read my previous post and setup your file associations accordingly!
For me it still works fine!
+Lior Sion I didn't.. I was never able to import the project, but the good thing is that if you create a new project, and just use that code, it will work perfect. Good luck!
Does this also give me access to the relatively new now that revision 18 is out?
+David Cruz I solved it - it was an issue with the minimum sdk version, which was previously 7 but the new sdk required 8
+René Köcher  Could you elaborate on "add '.aar' to the registered archive types in Android Studio settings". I don't see any registered archive types in the Android Studio Preferences.
+René Köcher Thanks, found it. I am still having issues getting Android Studio to stop spewing "Cannot resolve method x" for support library functions even though it builds and runs.
Add a comment...