It seems that the incubating maven-publish plugin makes the scope of all dependencies in the generated pom runtime.
It’s a known issue, but I cannot find any limitation & issue for it. So I wonder whether it’s a known issue. Want to confirm.
http://stackoverflow.com/questions/20131915/publishing-artifact-from-gradle-project-to-bintray-maven-repository http://forums.gradle.org/gradle/topics/maven_publish_plugin_generated_pom_making_dependency_scope_runtime