From e4cf5a90e0b6c66a075504ffe04f7eafb34c525d Mon Sep 17 00:00:00 2001
From: Xavier Ducrohet <xav@google.com>
Date: Fri, 6 Mar 2015 17:17:30 -0800
Subject: workaround for aar dependencies in pom.

Apparently depending on a non jar dependency in
a pom must include the type of the dependency, even though
the dependency declares its own type in its pom.

Since Gradle doesn't properly do this, a workaround
is to customize the pom on the fly to do this (until Gradle
is fixed).

Change-Id: Id39ae4b4183e621ba1295ae8ee840fd0125e5d6e
---
 build.gradle | 5 +++++
 1 file changed, 5 insertions(+)

(limited to 'build.gradle')

diff --git a/build.gradle b/build.gradle
index 9ac4cd82f4..d364879637 100644
--- a/build.gradle
+++ b/build.gradle
@@ -147,6 +147,11 @@ subprojects {
         }
     }
 
+    def deployer = release.repositories.mavenDeployer
+    deployer.pom*.whenConfigured { pom ->
+        pom.dependencies.findAll {dep -> dep.groupId == 'com.android.support' && dep.artifactId != 'support-annotations' }*.type = 'aar'
+    }
+
     // before the upload, make sure the repo is ready.
     release.dependsOn rootProject.tasks.prepareRepo
     // make the mainupload depend on this one.
-- 
cgit v1.2.3