Support PCT for multi-module Maven projects (II)

[jglick]

Subsumes #685 but should allow jenkins-infra/repository-permissions-updater#3210 to be reverted, cleaning up technical debt from #612. Local testing seems fine using both a clean working copy and a clean local repo:

mvn clean test -Dtest=CpsDefaultGroovyMethodsTest

[basil]

Failed PCT against the multimodule project branch. Note that #685 passes.

• Testing https://github.com/jenkinsci/workflow-cps-plugin/pull/689 bom#1899
• https://ci.jenkins.io/job/Tools/job/bom/job/PR-1899/2/consoleFull

What goal are you trying to achieve by continuing to dig into this?

[jglick]

mvn test worked but mvn surefire:test (even after previous compilation) did not; I think I have fixed that.

[basil]

The latest revision passes local PCT testing for me on the multimodule project branch. Still not sure it was worth the effort.

[jglick]

https://github.com/jenkinsci/workflow-cps-plugin/releases/tag/3651.ve2e99a_4f4a_e5

[basil]

Breaks the master branch of PCT, unlike my original proposal from #685 (which works on both the master and multimodule branches of PCT). Can be seen by running PLUGINS=workflow-cps TEST=InjectedTest bash local-test.sh in jenkinsci/bom#1903.

I suggest that you either figure out how to get your code to work on both PCT branches or that you accept my original submission (which does work on both branches), even if you consider it "undesirable". You can always switch back to your code once the PCT multimodule project has been integrated.