Hi, I am trying to enable dependabot to find the release notes from our plugin I added the url here, but it seems to be the wrong pom file. I tried registering another publication:

publishing {
    publications {
      register("pluginMaven", MavenPublication::class) {
        pom {
          url.set("<https://github.com/europace/docker-publish-gradle-plugin>")
        }
      }
      register("dockerPublishPluginPluginMarkerMaven", MavenPublication::class) {
        pom {
          url.set("<https://github.com/europace/docker-publish-gradle-plugin>")
        }
      }
    }
  }
}

But I get the error:

> Cannot add a Publication with name 'dockerPublishPluginPluginMarkerMaven' as a Publication with that name already exists.

Any idea what I am doing wrong? I could not find any documentation about the adaption of the pom file. Here they mention the publications, but I do not understand how to enrich the root pom file

The plugin publish plugin already creates those publications for you. By using

register

you try to also create them and thus get the error that the publication already exists. Use

named(...)

instead of

register(...)

to get the already existing publication and then just configure that already existing publication.

@Vampire thanks for your answer. When I change the

register

to

named

I get this error:

Publication with name 'dockerPublishPluginPluginMarkerMaven' not found.

Any Idea what I am doing wrong? The whole plugin section is:

gradlePlugin {
  website.set("<https://github.com/europace/docker-publish-gradle-plugin>")
  vcsUrl.set("<https://github.com/europace/docker-publish-gradle-plugin>")
  plugins {
    create("dockerPublishPlugin") {
      id = "de.europace.docker-publish"
      displayName = "Docker Publish Plugin"
      description = "Adds tasks to create and publish a Docker image to a registry"
      implementationClass = "de.europace.gradle.docker.publish.DockerPublishPlugin"
      tags.set(listOf("docker", "publish", "publishing"))
    }
  }
  publishing {
    publications {
      named("dockerPublishPluginPluginMarkerMaven", MavenPublication::class) {
        pom {
          url.set("<https://github.com/europace/docker-publish-gradle-plugin>")
        }
      }
    }
  }
}

Maybe it is registered after that point. If you anyway want to set this on all publications, I'd just do

publications.withType(MavenPublication::class).configureEach { ... }

. If not, then something like

publications.withType(MavenPublication::class).named { it == "..." }.configureEach { ... }

.

@Vampire sorry I was on holiday. many thanks for the help, it worked now 🙂

It's the other way around. You do add it to the main pom: https://plugins.gradle.org/m2/de/europace/gradle/docker-publish-gradle-plugin/2.0.10/docker-publish-gradle-plugin-2.0.10.pom You miss to do it on the plugin marker artifact: https://plugins.gradle.org/m2/de/europace/docker-publish/de.europace.docker-publish.gr[…]/2.0.10/de.europace.docker-publish.gradle.plugin-2.0.10.pom

but I thought I add it to all publications, so I am confused 🙈

Hm, strange, looks fine to me and also works when publishing to maven local 😕

Yeah that is my problem and that is why I keep making pull requests 🙈

BTW is the plugin open sourced? If not, I never managed to get the release notes of an internal dependency.

@Philip W sure, the URL is right in the OP where she shows how she configures it 🙂

Our plugin repo is here 🙂

The plugin marker POMs are generated by the plugin portal (or the plugin publish plugin) and you can't do anything about it: https://github.com/gradle/plugin-portal-requests/issues/212

@Thomas Broyer thanks for the link. in there they mention that it should work though, or did I understand this comment wrongly?

From the same author, ~3 years later: https://github.com/gradle/plugin-portal-requests/issues/212#issuecomment-1948248286

Thanks. I added a comment on that issue and hopefullt I get an answer 🙂