# Confusion over plugin dependencies

**URL:** <https://discuss.gradle.org/t/confusion-over-plugin-dependencies/21212>\
**Category:** Help/Discuss\
**Created:** [January 18, 2017, 11:47pm UTC](https://discuss.gradle.org/t/confusion-over-plugin-dependencies/21212 "2017-01-18T23:47:12Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![sc1478](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/sc1478/32/4341_2.png) [@sc1478](https://discuss.gradle.org/u/sc1478)\
**Post date:** [January 27, 2017, 3:09pm UTC](https://discuss.gradle.org/t/confusion-over-plugin-dependencies/21212/10 "2017-01-27T15:09:19Z")

</div>

> [@sc1478](#):
>
> Unless there is some reason why the single repo with artifactUrls is bad practice, I think I prefer that way because it is a single block.

There is a reason why it is bad practice. If I want to publish back to the corporate repo, I need to apply credentials. If I tell gradle that[https://plugins.gradle.org/m2/](https://plugins.gradle.org/m2/) is part of my nexus repository, it will try to apply those credentials there. Thus it works best to have my corporate nexus as one repository and the gradle plugin rep as two maven repositories.

---

_[View the full topic](https://discuss.gradle.org/t/confusion-over-plugin-dependencies/21212)._