Exclusion is no longer needed

[Vlatombe]

Fixes

[2022-10-13T07:50:05.173Z] [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.apache.maven.plugins:maven-enforcer-plugin @ org.jenkins-ci.main:jenkins-test-harness:${changelist}, /home/jenkins/workspace/Core_jenkins-test-harness_PR-499/pom.xml, line 290, column 15

Stapler actually pulls guava 11.0.1 so there doesn't seem to be an upperboundcheck problem.
jenkinsci/stapler#123

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[jglick]

https://issues.jenkins.io/browse/JENKINS-36779 closed in 2.320. For now

jenkins-test-harness/pom.xml

Line 59 in e5ab6d2

<jenkins.version>2.249</jenkins.version>

but we will probably need to move to 2.361.x at some point (#453).

[basil]

Still needed so long as the test harness still supports Jenkins versions prior to 2.320 as far as I can tell.

[jglick]

🤔 how could that be? CI passes and this is just removing plugin configuration for this project, which should not affect the flattened form or at least not be relevant for projects consuming this as a dependency?

[basil]

which should not affect the flattened form

You are right, I was thinking about plugin-pom instead. Sorry.