external libraries management issue

KarelHusa, krsfst first of all, thank you for your advice. I have finally resolved my issue. Thanks to AI, I understood where my mistake came from.
The soapUI application has no issue. The external libraries are correctly imported at the application’s launch.
Indeed, I do have logs of the type ‘INFO: Adding […jar] to extension classpath’ following the application’s launch.
However, one of them uses (or imports) an org.apache.log4j library which is deprecated.
Hence the error message ‘Could not initialize class …’.
To fix my issue, I have therefore updated the external library so that it no longer references the deprecated library, but the one supported by soapUI (org.apache.logging.log4j).

I just upgraded from 5.6.0 to 5.7.0

I experience the same problem kbertran99 reports.

The jarfile in question has been copied into c:\Users\username\AppData\Local\SmartBear\SoapUI-5.7.0\bin\ext\

Groovy in SoapUI says: "unable to resolve class packagename.classname"

The classfiles within the jar were compiled using groovyc 3.0.8, the jarfile was created using JDK 1.8.0_211

Hi kbertran99 ,

can you please decribe the issue in more detail?

I use SoapUI 5.7.0 and custom jars within bin/ext directory and they seem to work fine.

In the log file all of the libraries are succesfully added, e.g.:

INFO:Adding [C:\Program Files\SmartBear\SoapUI-5.7.0\bin\ext\soapui-libs-1.6.5.jar] to extensions classpath

There are no "could not initialize class ..." errors in the log file (as were in the past). 

Best regards,

Karel