From eb9149baab9011ab40ba637d408c8fbfbd4a874a Mon Sep 17 00:00:00 2001
From: Marcin Zajaczkowski <szpak@users.sourceforge.net>
Date: Mon, 2 Mar 2015 21:39:39 +0100
Subject: [PATCH] Fix broken dependencies' scope in pom.xml

Known limitation in maven-publish:
http://forums.gradle.org/gradle/topics/maven_publish_plugin_generated_pom_making_dependency_scope_runtime#reply_14120711
---
 build.gradle | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/build.gradle b/build.gradle
index c67ab2c5a8..9372d26f62 100644
--- a/build.gradle
+++ b/build.gradle
@@ -57,6 +57,17 @@ subprojects {
 		publications {
 			maven(MavenPublication) {
 				from components.java
+				pom.withXml {
+					//#89 - workaround to not to have only runtime dependencies in generated pom.xml
+					//Known limitation in maven-publish - - http://forums.gradle.org/gradle/topics/maven_publish_plugin_generated_pom_making_dependency_scope_runtime#reply_14120711
+					asNode().dependencies.'*'.findAll() {
+						it.scope.text() == 'runtime' && project.configurations.compile.allDependencies.find { dep ->
+							dep.name == it.artifactId.text()
+						}
+					}.each() {
+						it.scope*.value = 'compile'
+					}
+				}
 			}
 		}
 	}