I'd guess it is a temporary issue caused by JCasC test dependency being higher than your current version of Plugin POM. JCasC test harness depends on JTH explicitly.
IMHO it is time to make one step forward and to include JCasC test harness and into Jenkins Test Harness or to Plugin POM by default. There is wide adoption of JCasC test automation thanks to so many contributors, and IMHO there is no particular point in making users to explicitly define it these days. Opinions? On Tuesday, September 14, 2021 at 11:44:57 AM UTC+2 Chris Kilding wrote: > 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/033ceeaf-187a-4012-9f7a-c576d172fdfcn%40googlegroups.com.
