Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Pipeline Model Definition API 1.7.1
Jenkins 2.235.2
-
-
pipeline-model-definition 1.7.2
Description
There is a risk of binary compatibility conflict there
Require upper bound dependencies error for com.google.guava:guava:11.0.1 paths to dependency are:
+-io.jenkins.jenkinsfile-runner:payload-dependencies:1.0-beta-13-SNAPSHOT
+-org.jenkins-ci.main:jenkins-core:2.235.2
+-com.google.guava:guava:11.0.1
and
+-io.jenkins.jenkinsfile-runner:payload-dependencies:1.0-beta-13-SNAPSHOT
+-org.jenkins-ci.main:jenkins-core:2.235.2
+-org.kohsuke.stapler:stapler-jrebel:1.259
+-org.kohsuke.stapler:stapler:1.259
+-com.google.guava:guava:11.0.1
and
+-io.jenkins.jenkinsfile-runner:payload-dependencies:1.0-beta-13-SNAPSHOT
+-io.jenkins.plugins:pipeline-as-yaml:0.10-rc-SNAPSHOT
+-org.jenkinsci.plugins:pipeline-model-definition:1.7.1
+-org.jenkinsci.plugins:pipeline-model-api:1.7.1
+-com.github.fge:json-schema-validator:2.0.4
+-com.github.fge:json-schema-core:1.0.4
+com.google.guava:guava:11.0.1 (managed) <- com.google.guava:guava:13.0.1
FWIW, I don't see any issues with the version picked up by pipeline-model-api itself, so I think this is specific to artifacts that depend on it. Easy enough to add an exclusion to avoid the problem.