Version mismatch from external jars
Hi, I currently have a problem regarding loading external jars into soapUI pro. We have a jar that is build inhouse but depending on other jars (nested), in this case slf4j (version 1.6.1). As ...
Forum Discussion
Thanks for the response!
Well yes I have tried that and it solves slf4j issue, but then I fail on the next dependent jar.
That could go on for a lot of common libraries, I don't really know how many right now.
And I'm not to confident that it is the best solution to change versions of the jars that soapUI needs.
That could result in a unstable soapUI client.
And in the end it will result that all testers with a soapUI client also would need to replace the jars which complicates it even more.
So I guess that the bin/ext and lib loading is tightly coupled to the same classpath?
Well yes I have tried that and it solves slf4j issue, but then I fail on the next dependent jar.
That could go on for a lot of common libraries, I don't really know how many right now.
And I'm not to confident that it is the best solution to change versions of the jars that soapUI needs.
That could result in a unstable soapUI client.
And in the end it will result that all testers with a soapUI client also would need to replace the jars which complicates it even more.
So I guess that the bin/ext and lib loading is tightly coupled to the same classpath?