Thanks to everyone who has adopted the new Spotless configuration. I am trying to get everyone who was already using Spotless migrated over to the new configuration. Once that happens, I might even be able to change the opt-in mechanism from the ugly .mvn_exec_spotless file to a Maven property.
The next question is: do we want to do the same thing for core and core components? And if so, do we want it to be opt-in or shall we apply Spotless unconditionally for core and all core components? I can do the work, but it would take some time to cover all components. The question boils down to whether or not the other maintainers are comfortable with this change. The last time we did a large formatting change in core (adding Prettier) the usual concerns were expressed regarding merge conflicts in open PRs and difficulty of backports. I think we did a pretty good job of resolving merge conflicts in open PRs, and we backported the formatting change in order to address concerns from the security team. We could adopt that (successful) strategy again in this case, assuming the same concerns still apply. -- 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/CAFwNDjpOAQR88KOyxCYzdqE9h5-80qkugm1tnBXyex-nrmVrEA%40mail.gmail.com.
