As explained by Jesse in https://github.com/jenkins-infra/pipeline-library/pull/541#issuecomment-1342884874, changing the default of buildPlugin() could create problems. I'll close the PR as there is no value in changing the default as it.
The archetypes used to generate a new plugin project are already up to date: there is a documentation effort to be done that would be much more valuable (I heard that some documentation contributors are going to propose help) which make sense. Eventually, once the documentation is up to date, we could add a message when "buildPlugin()" is called without argument, recomending to list explicit configurations. Le mercredi 7 décembre 2022 à 16:51:06 UTC+1, Damien Duportal a écrit : > Prepared the draft PR for "buildPlugin()": > https://github.com/jenkins-infra/pipeline-library/pull/541 > > Le jeudi 1 décembre 2022 à 19:16:40 UTC+1, m...@basilcrow.com a écrit : > >> I released the first tranche of PRs in 4.52 >> <https://github.com/jenkinsci/plugin-pom/releases/tag/plugin-4.52>. Next >> week I will take a look at migrating from Jetty 9 to Jetty 10 in the plugin >> build toolchain. >> > -- 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/face200b-1265-4e42-9194-eb2a46f00916n%40googlegroups.com.
