Forum Discussion
sbrey
12 years agoOccasional Contributor
The reason for the misbehavior/bug of LoadUI 2.7 is quite clear:
Examination of Bundle:
maven@cbsload01:~/SmartBear/LoadUI-2.7.0/bundle/tmp> jar tvf loadui-soapui-plugin-2.7.0.jar | grep groovy
5956300 Wed Nov 20 12:03:50 CET 2013 groovy-all-1.8.0.jar
maven@cbsload01:~/SmartBear/LoadUI-2.7.0/bundle/tmp>
means:
HINT: LoadUI SoapUI bundle is again packaged with the old groovy 1.8.0 jar , so suites depending on standard groovy 2.0 featuers (which works perfectly for SoapUI product (based on groovy 2) have to fail !!!
At the moment LoadUI is only supporting out-dated Groovy 1.8 scripts, SoapUI however Groovy 2.x scripts.
Examination of Bundle:
maven@cbsload01:~/SmartBear/LoadUI-2.7.0/bundle/tmp> jar tvf loadui-soapui-plugin-2.7.0.jar | grep groovy
5956300 Wed Nov 20 12:03:50 CET 2013 groovy-all-1.8.0.jar
maven@cbsload01:~/SmartBear/LoadUI-2.7.0/bundle/tmp>
means:
HINT: LoadUI SoapUI bundle is again packaged with the old groovy 1.8.0 jar , so suites depending on standard groovy 2.0 featuers (which works perfectly for SoapUI product (based on groovy 2) have to fail !!!
At the moment LoadUI is only supporting out-dated Groovy 1.8 scripts, SoapUI however Groovy 2.x scripts.