Problem Description
json-path:2.1.0 introduces json-smart:2.2, accessors-smart:1.1 and asm:5.0.3. But these jar files contain conflict classes with the same full qualified name, making it a mess.
[INFO] +- com.jayway.jsonpath:json-path:jar:2.1.0:test
[INFO] | \- net.minidev:json-smart:jar:2.2:test
[INFO] | \- net.minidev:accessors-smart:jar:1.1:test
[INFO] | \- org.ow2.asm:asm:jar:5.0.3:test
All three dependencies contain conflict asm classes like
[org.objectweb.asm.ClassWriter, org.objectweb.asm.AnnotationVisitor,org.objectweb.asm.MethodVisitor,org.objectweb.asm.FieldWriter, ...]
To make matters worth, json-smart and accessor-smart contain addtional conflict classes like
[net.minidev.asm.ASMUtil, net.minidev.asm.ex.NoSuchFieldException, net.minidev.asm.ConvertDate, ...]
Possible Solution
Fortunately, json-path:2.4.0 uses upgraded json-smart and accsessors-smart which remove all the conflict classes. So upgrading to json-path 2.4.0 seems a good choice.
[INFO] +- com.jayway.jsonpath:json-path:jar:2.4.0:test
[INFO] | +- net.minidev:json-smart:jar:2.3:test
[INFO] | | \- net.minidev:accessors-smart:jar:1.2:test
[INFO] | | \- org.ow2.asm:asm:jar:5.0.4:test
I upgrade the json-path version from 2.1.0 to 2.4.0 and run the tests. The test results are just as they were, everything seems fine.
Problem Description
json-path:2.1.0 introduces json-smart:2.2, accessors-smart:1.1 and asm:5.0.3. But these jar files contain conflict classes with the same full qualified name, making it a mess.
All three dependencies contain conflict asm classes like
To make matters worth, json-smart and accessor-smart contain addtional conflict classes like
Possible Solution
Fortunately, json-path:2.4.0 uses upgraded json-smart and accsessors-smart which remove all the conflict classes. So upgrading to json-path 2.4.0 seems a good choice.
I upgrade the json-path version from 2.1.0 to 2.4.0 and run the tests. The test results are just as they were, everything seems fine.