Forum Discussion

olgasson's avatar
olgasson
13 years ago

maven soapui pro plugin 4.0.1 problem

Hi,

I had maven soapui plugin 4.0.1 running normal. Now i tried the trial pro plugin and at execution the following error occurs:

[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
at java.lang.ClassLoader.checkCerts(ClassLoader.java:943)
at java.lang.ClassLoader.preDefineClass(ClassLoader.java:657)
at java.lang.ClassLoader.defineClass(ClassLoader.java:785)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195)
at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255)
at org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at com.eviware.soapui.maven2.TestMojo.execute(TestMojo.java:50)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10 seconds
[INFO] Finished at: Tue Oct 25 15:33:40 CEST 2011
[INFO] Final Memory: 13M/32M
[INFO] ------------------------------------------------------------------------



I have no idea what causes it. Thanks for any hint.

Regards

10 Replies

Sort By
  • mikey0's avatar
    mikey0
    New Contributor
    13 years ago
    Was there ever a resolution for this? I'm experiencing the same behavior.
  • calandale's avatar
    calandale
    Occasional Contributor
    13 years ago
    Seeing it here too - 4.0.2-SNAPSHOT seems to have resolved this.
  • al0's avatar
    al0
    Occasional Contributor
    13 years ago
    For me 4.0.2 results into a much more basic error

    [ERROR] Plugin eviware:maven-soapui-pro-plugin:4.0.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for eviware:maven-soapui-pro-plugin:jar:4.0.2-SNAPSHOT: Could not find artifact eviware:maven-soapui-pro-plugin:pom:4.0.2-SNAPSHOT -> [Help 1]
    13-Mar-2012 15:26:42 org.apache.maven.plugin.PluginResolutionException: Plugin eviware:maven-soapui-pro-plugin:4.0.2-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for eviware:maven-soapui-pro-plugin:jar:4.0.2-SNAPSHOT
    13-Mar-2012 15:26:42 at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129)
    13-Mar-2012 15:26:42 at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142)
    13-Mar-2012 15:26:42 at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:261)
    13-Mar-2012 15:26:42 at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:185)
    13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:152)
    13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecutions(DefaultLifecycleExecutionPlanCalculator.java:139)
    13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:116)
    13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:129)
    13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.BuilderCommon.resolveBuildPlan(BuilderCommon.java:92)
    13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
    13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
    13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
    13-Mar-2012 15:26:42 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
    13-Mar-2012 15:26:42 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
    13-Mar-2012 15:26:42 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
    13-Mar-2012 15:26:42 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
    13-Mar-2012 15:26:42 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
    13-Mar-2012 15:26:42 at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
    13-Mar-2012 15:26:42 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    13-Mar-2012 15:26:42 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    13-Mar-2012 15:26:42 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    13-Mar-2012 15:26:42 at java.lang.reflect.Method.invoke(Method.java:597)
    13-Mar-2012 15:26:42 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
    13-Mar-2012 15:26:42 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
    13-Mar-2012 15:26:42 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
    13-Mar-2012 15:26:42 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
    13-Mar-2012 15:26:42 Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for eviware:maven-soapui-pro-plugin:jar:4.0.2-SNAPSHOT
    13-Mar-2012 15:26:42 at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:296)
    13-Mar-2012 15:26:42 at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:186)
    13-Mar-2012 15:26:42 at org.sonatype.aether.impl.internal.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:279)
    13-Mar-2012 15:26:42 at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:115)
    13-Mar-2012 15:26:42 ... 25 more
    13-Mar-2012 15:26:42 Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could not find artifact eviware:maven-soapui-pro-plugin:pom:4.0.2-SNAPSHOT
    13-Mar-2012 15:26:42 at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
    13-Mar-2012 15:26:42 at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
    13-Mar-2012 15:26:42 at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:193)
    13-Mar-2012 15:26:42 at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:281)
    13-Mar-2012 15:26:42 ... 28 more
    13-Mar-2012 15:26:42 Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not find artifact eviware:maven-soapui-pro-plugin:pom:4.0.2-SNAPSHOT
    13-Mar-2012 15:26:42 at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:528)
    13-Mar-2012 15:26:42 ... 31 more

    Note, that if I change to 4.0.0 or 4.0.1 no artifact resolution issues arise.
    And eviware repository in in the POM

        <pluginRepositories>
            <pluginRepository>
                <id>maven2-eviware-repository</id>
                <name>Eviware Maven 2 Repository (for SoapUI)</name>
                <url>http://www.eviware.com/repository/maven2/</url>
                <snapshots>
                    <enabled>false</enabled>
                </snapshots>
            </pluginRepository>
        </pluginRepositories>
  • al0's avatar
    al0
    Occasional Contributor
    12 years ago
    Thanks redfish4ktc, so stupid from me, that I have not noticed it myself.
  • snoll's avatar
    snoll
    Occasional Contributor
    12 years ago
    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.
  • redfish4ktc2's avatar
    redfish4ktc2
    Super Contributor
    12 years ago
    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
  • snoll's avatar
    snoll
    Occasional Contributor
    11 years ago
    Well, thanks for your help. Our solution was to put correct versions in our self hosted artifactory repository that has priority over the mirrored one.

    Regards
    Stephan
  • redfish4ktc2's avatar
    redfish4ktc2
    Super Contributor
    11 years ago
    Ok, thanks for the feedback, I will release my plugin, I have some collegues who need it anyway