hello! any idea why publish to sonatype would not include my custom gradle plugin.jar? I’m publishing to both Maven Central (through

publish

) and Plugin Portal (

publishPlugin

) and while last publish was successful I only got pom, module, javadoc and sources (from default maven publication) but no jar (in sonatype). My root project config: https://github.com/ExpediaGroup/graphql-kotlin/blob/master/build.gradle.kts#L172 <- I’m explicitly configuring 

mavenJava

 publication for all projects except Gradle plugin as it explicitly creates its own 

pluginMaven

 publication. Gradle plugin config: https://github.com/ExpediaGroup/graphql-kotlin/blob/master/plugins/graphql-kotlin-gradle-plugin/build.gradle.kts

publishToMavenLocal

 correctly publishes the plugin jar so it would appear that 

pluginMaven

 publication already contains the jar -> any ideas?

Just out of curiosity: why are you interested in publishing a plugin to Sonatype? Isn’t Gradle Portal already enough?

Afaik Gradle Portal would cover most of the use cases but there are some fringe cases (eg private artifactories that only sync to Maven Central - you would specify dependency on plugin in buildscript) that might not work

Instead of creating a new publication

mavenJava

you can simply override details of the publication the java-gradle-plugin will be creating. I think it's called

pluginMaven

.

Yep thats what I do (default mavenJava is created for all other libs)