RE: Wiremock 3.0.1 - I have a question and it's re...
# general
m
RE: Wiremock 3.0.1 - I have a question and it's related to some constraints applied for json-smart 2.5.0. I will create a thread ๐Ÿงต
Hello, The issue I am reporting here started happening when we moved to wiremock versin 3.0.1. The issue is specific to json-smart and json-path. The dependency analysis in my gradle file says that versions between the above projects are in conflict now. I observed this because all our imports of JSONObject and JSONParser classes were having errors. here is my build.gradle file if you fancy a reproduction of the issue.
Copy code
plugins {
    id 'java'
}

group = 'org.example'
version = '1.0-SNAPSHOT'

repositories {
    mavenCentral()
}

dependencies {
    testImplementation "com.github.tomakehurst:wiremock-jre8:3.0.1"
    testImplementation platform('org.junit:junit-bom:5.10.0')
    testImplementation 'org.junit.jupiter:junit-jupiter'
}

test {
    useJUnitPlatform()
}
my question - What is the recommendation here? i.e the recommended course of action?
l
Hi. I am not sure I understand your issue. Can you post the results of your dependency analysis. I am not sure which versions would be in conflict ?
Are you referring to this constraint :
Copy code
constraints {
    implementation "net.minidev:json-smart:2.5.1", {
      because 'Pinning this above the transitive version from json-path to get CVE fix'
    }
  }
m
Yes I am - I think I will simply replace the usage of those JSON* classes as Jackson or Gson is a more affordable option for me. You can ignore my question for now ๐Ÿ™‚
๐Ÿ‘ 1