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

Gradle Community

I can hardly guess what your setup is as you don't show what you have.
But I guess you should simply configure the publications added by the plugin instead of adding own publications.

publishing -&gt; <https://github.com/ExpediaGroup/graphql-kotlin/blob/master/build.gradle.kts#L115>

plugin -&gt; <https://github.com/ExpediaGroup/graphql-kotlin/blob/master/plugins/graphql-kotlin-gradle-plugin/build.gradle.kts>

updated the main build file with
```val publicationName = if (currentProject.name == "graphql-kotlin-gradle-plugin") {
  "mavenPlugin"
} else {
  "mavenJava"
}```
so it picks the right name

Well, using `subprojects { ... }` is evil, but you probably know that.
But well, it is like I said.
With the "wrong" name you try to add a second publication for the same coordinates.
With the "correct" name you try to add a second publication with the same name and for the same coordinates.
For the plugin project do not try to create a new publication but configure the one that gets added by the plugin as I already said. :slightly_smiling_face:

yeah need to update the build to buildSrc one of those days

&gt; For the plugin project do not try to create a new publication but configure the one that gets added by the plugin as I already said. :slightly_smiling_face:
this is automatically added by the gradle plugin publish vs reusing the same one

guess in the subprojects i can only create maven project if not gradle plugin

Yes, that's exactly what I said two times already.
Do not try to create a new one, but configure the one that is added by the plugin.

&gt; yeah need to update the build to buildSrc one of those days
Actually, I would right away use an included build instead. :slightly_smiling_face: