-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Component/s: pipeline-model-definition-plugin
-
Labels:None
-
Similar Issues:
Fun with Jackson version conflicts! The jackson2-api plugin has newer Jackson jars that barf against the json-schema-validator version we're using. Sigh.
- links to
PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/111, shading away Jackson.
Code changed in jenkins
User: Andrew Bayer
Path:
pipeline-model-api/pom.xml
pipeline-model-definition/pom.xml
pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/Converter.groovy
pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/JSONParser.groovy
pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/endpoints/ModelConverterAction.java
pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BaseParserLoaderTest.java
pipeline-model-json-shaded/pom.xml
pom.xml
http://jenkins-ci.org/commit/pipeline-model-definition-plugin/7a06eb4fce798ddfe12d220106d76b7744c6096a
Log:
[FIXED JENKINS-41911] Shade away Jackson
This took some hoop-jumping, but now we should be guaranteed to use
our own copy of Jackson at all times. Phew.
Merged, releasing shortly as 1.0.1.
Bulk closing resolved issues.
And I just remembered why we're on the 2.0.4 release of json-schema-validator (which uses old 2.2.x jackson): because the newer train of json-schema-validator (2.2.x, which uses 2.7.x jackson) also needs Guava 16. Ffffffff. Right. Time to remember how to shade.