-
Notifications
You must be signed in to change notification settings - Fork 354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecated method of commons-lang #1378
Comments
Can you share you pom file? Pitest doesn't share its classpath with the code under test (except for within child processes where a minimal number of dependencies exist, all of which are meant to be shaded), so library version mismatches shouldn't happen. |
Please find below. However its working fine with version 1.17.0 0.95 0.83 2.16.1 ${jackson.core.version} 5.10.0 1.10.0 1.11.311 4.30.0 5.2.0 2.23.1 3.1.0 95 85 1.17.0 1.2.1 17 17 org.liquibase liquibase-core ${org.liquibase.version} test org.glassfish.jersey.inject jersey-hk2 ${jersey.version} org.glassfish.jersey.test-framework.providers jersey-test-framework-provider-grizzly2 ${jersey.version} test org.glassfish.jersey.test-framework.providers jersey-test-framework-core ${jersey.version} test org.glassfish.jersey jersey-bom ${jersey.version} pom import org.glassfish.jersey.ext jersey-bean-validation ${jersey.version} javax javaee-api 7.0 org.postgresql postgresql 42.7.3 com.amazonaws aws-java-sdk-bom ${aws-sdk.version} pom import jakarta.ws.rs jakarta.ws.rs-api ${jakarta.version} compile org.yaml snakeyaml 2.0 org.apache.commons commons-lang3 3.17.0 com.github.ben-manes.caffeine caffeine 3.1.8 com.squareup.okhttp3 okhttp 4.12.0 com.fasterxml.jackson.datatype jackson-datatype-jsr310 ${jackson.core.version} com.fasterxml.jackson.core jackson-databind ${jackson.databind.version} com.google.code.gson gson 2.9.0 org.apache.logging.log4j log4j-api ${log4j.version} org.apache.logging.log4j log4j-core ${log4j.version} org.apache.logging.log4j log4j-slf4j-impl ${log4j.version} org.junit.jupiter junit-jupiter ${junit5.version} test org.junit.platform junit-platform-commons ${junit5.platform.commons.version} test org.junit.jupiter junit-jupiter-params ${junit5.version} test org.mockito mockito-core ${mockito.version} test org.mockito mockito-junit-jupiter ${mockito.version} test org.mockito mockito-inline ${mockito.version} test org.projectlombok lombok 1.18.28 provided com.fasterxml.jackson.core jackson-core ${jackson.core.version} compile org.jsoup jsoup 1.16.1 org.liquibase liquibase-core ${org.liquibase.version} test org.glassfish.jersey.test-framework jersey-test-framework-core ${jersey.version} test org.glassfish.jersey.inject jersey-hk2 ${jersey.version}
|
The reason you are seeing this with 1.17.4 is an upgrade to commons-text 1.12.0 in pitest entry, however the classpath of the maven plugin should be seperate from the classpath of your codebase. From the snippets of pom you have pasted it is unclear why there is a conflict. Could you post a minimal project that recreates the issue. |
Hi,
While running mutation test getting below error. It seems like due deprecated method usage in pitest. I am using 3.17.0 version of commons-lang3.
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution pit-test of goal org.pitest:pitest-maven:1.17.4:mutationCoverage failed: An API incompatibility was encountered while executing org.pitest:pitest-maven:1.17.4:mutationCoverage: java.lang.NoSuchMethodError: 'org.apache.commons.lang3.Range org.apache.commons.lang3.Range.of(java.lang.Comparable, java.lang.Comparable)'
The text was updated successfully, but these errors were encountered: