# Maven-publish plugin makes the scope of all dependencies in the generated pom runtime

**URL:** <https://discuss.gradle.org/t/maven-publish-plugin-makes-the-scope-of-all-dependencies-in-the-generated-pom-runtime/896>\
**Category:** Old Forum Archive\
**Created:** [December 26, 2014, 11:35am UTC](https://discuss.gradle.org/t/maven-publish-plugin-makes-the-scope-of-all-dependencies-in-the-generated-pom-runtime/896 "2014-12-26T11:35:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Le\_Chen](https://avatars.discourse-cdn.com/v4/letter/l/278dde/32.png) [@Le\_Chen](https://discuss.gradle.org/u/Le_Chen)\
**Post date:** [December 26, 2014, 11:35am UTC](https://discuss.gradle.org/t/maven-publish-plugin-makes-the-scope-of-all-dependencies-in-the-generated-pom-runtime/896/1 "2014-12-26T11:35:00Z")

</div>

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://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](http://forums.gradle.org/gradle/topics/maven_publish_plugin_generated_pom_making_dependency_scope_runtime)