While working on a different core PR, I noticed this plugin was using vanilla XStream rather than the Jenkins-specific XStream2 in one test. Since we generally prefer XStream2, and since using XStream2 doesn't make the test start failing, I thought it would be best to make this usage consistent with our general preference for XStream2.
While working on a different core PR, I noticed this plugin was using vanilla XStream rather than the Jenkins-specific XStream2 in one test. Since we generally prefer XStream2, and since using XStream2 doesn't make the test start failing, I thought it would be best to make this usage consistent with our general preference for XStream2.