Forum Discussion
redfish4ktc2
12 years agoSuper Contributor
snoll Hi, thanks for the feedback about the jar modification in the soapui repository.
Do not expect any rollback from SmartBear, they don't do any support on old version (expecially for maven artifacts)
When I checked for this issue almost a year ago, the soapui jar wasn't signed but the soapui-pro jar was signed! see https://github.com/redfish4ktc/maven-so ... nt-5981863
It seems this is still the case, I've just checked by downloading the 2 jars from the repository.
So, there is a workaround
The soapui jar file packaged in soapui is signed. You could upload it in your private repository with a different version (let's say 4.0.1.0) and use this version as dependency of the maven-soapui-pro-plugin
Do not expect any rollback from SmartBear, they don't do any support on old version (expecially for maven artifacts)
When I checked for this issue almost a year ago, the soapui jar wasn't signed but the soapui-pro jar was signed! see https://github.com/redfish4ktc/maven-so ... nt-5981863
It seems this is still the case, I've just checked by downloading the 2 jars from the repository.
So, there is a workaround
The soapui jar file packaged in soapui is signed. You could upload it in your private repository with a different version (let's say 4.0.1.0) and use this version as dependency of the maven-soapui-pro-plugin
Related Content
- 8 years ago
- 9 years ago
- 8 years ago
Recent Discussions
- 15 days ago
- 22 days ago