gradle / plugin-portal-requests

Gradle Plugin Portal issues and requests.
https://plugins.gradle.org/
12 stars 8 forks source link

Make the plugin coordinates pom file include url and scm tags #173

Open monosoul opened 1 year ago

monosoul commented 1 year ago

Expected Behavior

url and scm (and preferably all other) tags aren't removed when uploading the pom file

Current Behavior

url and scm tags are removed when uploading the pom file

Context

When publishing a plugin to Gradle plugin portal - it will create 2 pom files:

  1. One for the plugin (referring the jar file as a dependency) (e.g.: https://plugins.gradle.org/m2/org/jetbrains/kotlin/jvm/org.jetbrains.kotlin.jvm.gradle.plugin/1.7.22/org.jetbrains.kotlin.jvm.gradle.plugin-1.7.22.pom)
  2. One for the actual jar file (e.g.: https://plugins.gradle.org/m2/org/jetbrains/kotlin/kotlin-gradle-plugin/1.7.22/kotlin-gradle-plugin-1.7.22.pom)

The first pom file gets trimmed when uploaded to the plugin portal, to be specific: url and scm tags are removed. Because of that tools like renovatebot fail to fetch release notes and link the plugin sources.

For comparison, here's the first pom, but published to repo.maven.apache.org: https://repo.maven.apache.org/maven2/org/jetbrains/kotlin/jvm/org.jetbrains.kotlin.jvm.gradle.plugin/1.7.22/org.jetbrains.kotlin.jvm.gradle.plugin-1.7.22.pom .

GvcZhang commented 1 year ago

Mark.

ljacomet commented 2 months ago

Currently, marker POMs for Gradle plugins are generated on the server side when served from the Gradle Plugin Portal. This decision was made long ago and would be quite complicated to change.

We would need to consider the implications of changing what those files contain or decide to include that information only after a certain date.