Jesse Glick

compare https://github.com/jenkinsci/subversion-plugin/pull/288

https://github.com/XenitAB/spegel/blob/main/README.md#prerequisite makes it _sound_ straightforward enough.

Looks like this will be fixed in 25.0.1: https://github.com/moby/moby/pull/47161#event-11556363327 This worked for me on Ubuntu: ```bash sudo apt install docker-ce=5:24.0.7-1~ubuntu.22.04~jammy ``` (after identifying the old version from `/var/log/apt/history.log`)

See #462. I was nervous about enabling JEP-305 on this repo, but mainly it just needed testing.

@basil other than the merge conflict, is there anything holding this back?

> hesitance to move forward with this given your intent to subsequently enable JEP-229 That is an independent consideration. Enabling JEP-229 would simply be a subsuming PR. If you would...

This smells wrong. We do not want to keep `dependencyManagement`; we want the published POM to list the actual dependencies, no more nor less. Will discuss details in the issue.

Given https://github.com/jenkinsci/plugin-pom/issues/705#issuecomment-1463696163, should this be returned to draft?

Manual cleanup FTR ```groovy for (p in Jenkins.instance.getAllItems(Job)) { for (b in p.builds) { def a = b.getAction(hudson.tasks.junit.TestResultAction); if (a != null && !new File(b.rootDir, 'junitResult.xml').file) { println(b); b.removeActions(hudson.tasks.junit.TestResultAction); b.save();...

While this sounds fine as a hotfix, the proper fix would be to delete all the overrides and special cases handling and fix the form to use normal databinding by...