Let me go with option 2 and run tests using Groovy 4.0 locally. Thanks, Vladimir, for your input.
On Wed, Mar 2, 2022 at 2:25 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 > -- [image: photo] NaveenKumar Namachivayam Performance Engineer, QAInsights <http://github.com/qainsights> <http://youtube.com/qainsights> <http://us.linkedin.com/in/naveenkumarn> <http://twitter.com/qainsights> <http://facebook.com/naveenkumar%5C.namachivayam> [email protected] https://qainsights.com Cincinnati, OH
