Hi all, I've been maintaining the gradle-jpi-plugin for the last several years. I'm in support of this decision. My most recent OSS plugin used maven as well to take advantage of the excellent tooling the community has put together.
I elaborated a bit more on the mentioned issues in the repository <https://github.com/jenkinsci/gradle-jpi-plugin/issues/213#issuecomment-1355386081>, but wanted to share here as well. My main goal for maintaining this plugin is compatibility with new Gradle versions for the internal plugins I manage. Most of the evolution over the past several years have been in support of this. For example, there are now more than 400 acceptance tests that are easily run against arbitrary versions of Gradle (including pre-releases) and Java. I think feature parity with maven-hpi-plugin is achievable and would unlock some productivity gains, but I don't have the bandwidth or the need for this myself. I would be supportive of anyone who wanted to take that on. > Last I checked, generated poms were also invalid, which is a problem for any consumers of these artifacts that do more than just download the hpi. I believe this was fixed in 2019 as v0.31.0 <https://github.com/jenkinsci/gradle-jpi-plugin/releases/tag/v0.31.0>. Best, Steve On Friday, December 16, 2022 at 1:37:34 AM UTC-8 mc.ca...@gmail.com wrote: > I submitted a dedicated issue > <https://github.com/jenkinsci/gradle-jpi-plugin/issues/213> on the > plugin's repository outlining the TODOs and linking to this discussion. > > On Thursday, 8 December 2022 at 21:53:36 UTC+1 db...@cloudbees.com wrote: > >> On Wed, Dec 7, 2022 at 11:20 AM Alexander Brandes <mc.ca...@gmail.com> >> wrote: >> >>> There's no support for automated releases (CD, JEP-229), missing >>> metadata for the plugin page and a few other limitations, which don't make >>> it a great experience using it. >>> >> … >>> >> I would be ready to lift this restriction again if the JPI plugin >>> developers provide the same scope of tools like we have for Maven. >>> >> >> Is the maintainer of Gradle JPI Plugin aware of these requirements and/or >> this discussion? I don't see him in cc. >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/373899d7-a696-4748-a0c7-fcefccfe42een%40googlegroups.com.
