You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Expected Behavior
url
andscm
(and preferably all other) tags aren't removed when uploading the pom fileCurrent Behavior
url
andscm
tags are removed when uploading the pom fileContext
When publishing a plugin to Gradle plugin portal - it will create 2 pom files:
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
)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
andscm
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 .The text was updated successfully, but these errors were encountered: