Hi, I've seen the following dependency error in 2 plugins regarding jenkins-test-harness:
Require upper bound dependencies error for org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33 paths to dependency are: 22:20:04 +-io.jenkins.plugins:aws-secrets-manager-secret-source:0.0.2-SNAPSHOT 22:20:04 +-org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33 22:20:04 and 22:20:04 +-io.jenkins.plugins:aws-secrets-manager-secret-source:0.0.2-SNAPSHOT 22:20:04 +-io.jenkins.configuration-as-code:test-harness:1.52 22:20:04 +-org.jenkins-ci.main:jenkins-test-harness:1529.v4fd5bafdcd33 (managed) <-- org.jenkins-ci.main:jenkins-test-harness:1589.vc23fca066d5c Both projects use CasC, so they have been inheriting the actual jenkins-test-harness dependency transitively through config-as-code test harness. This was fine until BOM 937.v51fde92016ed, when the error started. Is it now necessary to include an explicit jenkins-test-harness dependency in a project's POM (to fix this), and if so is this stated anywhere? Regards, Chris -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e6219bea-d623-43d4-b488-727841b10bbc%40www.fastmail.com.
