Add Subversion to the managed set

[basil]

Adding Subversion (and its direct dependency MapDB API) to the managed set. It is used in the tests for workflow-multibranch, workflow-cps-global-lib, and workflow-scm-step, all of which need to bump their dependency and do a release whenever Subversion is updated, which is a bit annoying. That could be solved by including Subversion in the BOM. And yes, Subversion does need to be updated for recent versions of core because of the Digester removal.

[bitwiseman]

Let's see if the ASM change makes things work.

[jetersen]

based on discussion in jenkinsci/subversion-plugin#258 I'll disable auto merge 😅

[bitwiseman]

Okay... What the hell does this mean?
.2 passed all tests, but .3 failed. Is this the potential compat failure @basil was talking about? Basically, before .3 the plugin would use the plugin bundled version of ASM. With .3 it was excluded and now doesn't work? Or do we need to test the latest weekly?

Going back to subversion plugin to try again.

[basil]

Okay... What the hell does this mean?

I think all it means is that the Git client plugin's ModernScmTest needs to be adjusted. It assumes that Git is the only modern SCM, but when Subversion is added to the classpath (as PCT is doing here), there are now two modern SCMs: Git and Subversion, which the test is not expecting. So ModernScmTest needs to be adjusted to check that the list of modern SCMs contains Git rather than that it exclusively contains Git.

[basil]

=> jenkinsci/git-plugin#1093

[basil]

Run 3 is green, so I think this is ready for merge.

[jetersen]

@basil release is ready :)