+1 On Wed, Dec 7, 2022 at 2:20 AM Alexander Brandes <mc.cach...@gmail.com> wrote: > > Hey everyone, > > the Gradle JPI plugin lacks fundamental support of the jenkins.io > infrastructure. > 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. > > Additionally, worth to note, the components mentioned above aren't new. > People are proactively switching away from Gradle to Maven for better support > and acceptance of our tooling, see ivy-plugin/49 for example. > > For the reasons stated, I would like to propose, that new plugin hosting > requests use Maven, to have better toolchain support. > 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. > > Best, > Alexander Brandes, for the hosting team > > -- > 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/bb8f56d3-727b-481a-9132-17bf5eddbbcdn%40googlegroups.com.
-- 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/CAFwNDjq9xnyvJFoB33n07jORm7Hw6fSBf8FY5ho5FdGMDAiKug%40mail.gmail.com.
