Hi Vladimir, The Groovy 4.0.0 jar is not available in the following path. When I try to run the tests, I am getting the below error.
org.codehaus doesn't have Groovy 4.0.0 yet. Could you please advise? Thanks! > Could not resolve all files for configuration > ':src:bshclient:compileClasspath'. > Could not find org.codehaus.groovy:groovy-bom:4.0.0. Searched in the following locations: - https://repo.maven.apache.org/maven2/org/codehaus/groovy/groovy-bom/4.0.0/groovy-bom-4.0.0.pom - https://jcenter.bintray.com/org/codehaus/groovy/groovy-bom/4.0.0/groovy-bom-4.0.0.pom On 3/2/2022 2:25:10 AM, Vladimir Sitnikov <[email protected]> wrote: Hi, Judging by https://groovy-lang.org/releasenotes/groovy-4.0.html#Groovy4.0-naming-changes , the change is not backward-compatible. In other words, users' JMeter scripts might start failing for no apparent reason. So I would suggest: a) Plan Groovy 4 for JMeter 6. It does not mean we postpone Groovy4 to 2030. I would rather make an immediate PR for JMeter 5.5 saying like "Groovy 3 will be replaced with Groovy 4, so please follow the migration guide in Groovy 3/4 release notes if you use Groovy". b) Prepare a PR to flip Groovy from 3 to 4 to see if existing JMeter tests still pass. I am afraid it is infeasible to support multiple Groovy versions. It would be nice if multiple Groovy versions could coexist (e.g. as isolated JMeter plugins), however, I see no practical ways to implement it. WDYT? Vladimir [8ccd3fa8-685e-45cb-956e-a6eed50fad0e]
