Forum Discussion
snoll
12 years agoOccasional Contributor
olgasson wrote:
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] class "com.eviware.soapui.SoapUICore"'s signer information does not match
signer information of other classes in the same package
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.SecurityException: class "com.eviware.soapui.SoapUICore"'s signer info
rmation does not match signer information of other classes in the same package
I experienced the same problem with the soapui-maven-pro-plugin version 4.0.1
From one day to the next the error showed up.
After some analysis I found the reason:
<dependency>
<groupId>eviware</groupId>
<artifactId>soapui</artifactId>
<version>4.0.1</version>
</dependency>
In about august 2012 someone changed the binary of this artifact from unsigned to signed in the eviware repository.
http://www.eviware.com/repository/maven ... apui/4.0.1
Former SHA-1 Finperprint was fc9a060a921bcf38d18f83c2fc4c9f571d4a0163
Now SHA-1 Finperprint is fcab8ef810b5a3902abe4451fa9e2fd652786770
Generally it it not a good idea to change artifacts without updating the version number.
In our case we have a mirror cache repository that did not update because of the unchanged version number. So we noticed just a couple of days ago, when the cache was cleared.
However, since the soapui 4.0.1 artifact is signed now and soapui-pro 4.0.1 is not, but both share the same package names and are dependencies of maven-soapui-pro-plugin 4.0.1, the classloader gets into trouble.
Please revert soapui.jar 4.0.1 to unsigned jar again.
Related Content
- 8 years ago
- 8 years ago
- 9 years ago
Recent Discussions
- 15 days ago
- 22 days ago