Open bjhargrave opened 4 years ago
Thanks for opening this issue. It's great feature to have. It may overlap with some of the work around using the maven-publish
and the variant aware publishing that we are discussing but it's definitely something that should be doable from the plugin author.
You can absolutely hack this to make it work (I've done so in the past for some testing) but I agree we should expose an official way to do this.
FWIW I've submitted a workaround to bnd: https://github.com/bndtools/bnd/pull/3811
Expected Behavior
When wanting to publish an already built gradle plugin artifact in the Plugin portal, you want to use the existing pom file. See https://github.com/gradle/plugin-portal-requests/issues/9#issuecomment-566224151.
The
pluginBundle
DSL should provide a way to use the existing pom file (either as a supplied file or as the pom resource in the artifact jar) rather than always generating a new pom file.Current Behavior
The publish plugin always generates a new pom file which will not contain necessary information already in the existing pom file.
Context
See https://github.com/gradle/plugin-portal-requests/issues/9.