Confusion over plugin dependencies

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/ 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.