Com.gradle.plugin-publish does not honor dependency changes made in build.gradle

Our nebula-publishing-plugin takes dynamic and missing dependency versions and changes them to specific versions. The pom produced by the plugin-publish plugin is generating its own pom. Do we have hooks to modify the pom or can we have the plugin use the pom created for upload to jcenter/mavenCentral?


jcenter with no dynamic dependencies:

plugin portal with dynamic dependencies: curl -v -L

Having to skip using dynamic dependencies and our gradle-dependency-lock-plugin to keep resolves consistent via the portal.