Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
monosoul opened this issue Dec 22, 2022 · 2 comments
Open

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

monosoul opened this issue Dec 22, 2022 · 2 comments

Comments

@monosoul
Copy link

monosoul commented Dec 22, 2022

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
Copy link

GvcZhang commented Jun 1, 2023

Mark.

@ljacomet
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants