From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Are there any kind of migration instruction from previous versions? Trying it out I get
```Cannot add task 'signPluginMavenPublication' as a task with that name already exists.```


`signPluginMavenPublication` is the name of the signing task defined by the signing plugin when you instruct it to sign a publication named `pluginMaven`; since this new version of the Plugin-Publish plugin does all this automatically, if you have the signing plugin applied, I suspect that your build also does it explicitly; you would need to remove that; pls. provide a reproducer, if this doesn’t help

and indeed, migration guide starts to sound like “why didn’t we think of that”…

The "auto-configuration" might be an issue for me as I share the signing configuration between regular modules and plugin modules

FYI we are thinking about ways to best address this problem (ie. we aren’t ignoring you)

Thanks for the update :slightly_smiling_face: . No problem at all!

Let me know if I can help. The project I was testing the rc-2 with is <https://github.com/GradleUp/gr8/blob/main/build-logic/src/main/kotlin/gr8.build.publishing.gradle.kts#L150|this one>

(uses in-memory GPG keys. I have this setup in a lot of other projects to easily pull the keys from Github Actions)

fyi. fix merged in, will be in the next released version

That just got me thinking. Is the code for the Plugin-Publish open source ?

I can find <https://github.com/gradle/gradle/pull/20797|the commit that bumps the version in Gradle> but looks like the code is somewhere else?

yes, the plugin code is in a private repo, unfortunately

FYI RC3 with the fix is out, please give it a try.