+1 as well from me. Le jeu. 8 déc. 2022 à 17:19, Damien Duportal <damien.dupor...@gmail.com> a écrit :
> +1 > > Le mercredi 7 décembre 2022 à 15:49:42 UTC+1, bma...@gmail.com a écrit : > >> +1. >> >> At least such a move will make it very explicit for any new plugin that >> only Maven really has /production/ support for Jenkins plugin dev. >> >> I think that we should still "allow" new plugins to use Gradle if they >> wish so. But then they'll be very well aware that they got to be ready for >> a lot of pain and much meta-work around the tooling itself for developing >> their plugins. >> Which right now might be overlooked by new developers joining the >> community and thinking that choosing one or another is simply a matter of >> taste and habits. >> >> Le mer. 7 déc. 2022 à 15:19, Basil Crow <m...@basilcrow.com> a écrit : >> >>> +1 >>> >>> On Wed, Dec 7, 2022 at 2:20 AM Alexander Brandes <mc.ca...@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-de...@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-de...@googlegroups.com. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjq9xnyvJFoB33n07jORm7Hw6fSBf8FY5ho5FdGMDAiKug%40mail.gmail.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/5f43f822-37e4-45e2-85a2-3c60840ffcdfn%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/5f43f822-37e4-45e2-85a2-3c60840ffcdfn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAKwJSvwL_u384_cXKACe_kcuOQ%2Ba%2BgSxHCqcGbooHri0eQB%2BxA%40mail.gmail.com.
