Forum Discussion

bzzup's avatar
bzzup
Occasional Contributor
10 years ago

Exception when trying to use ReadyAPI maven plugin

Hi. We are trying to migrate our api tests from soapui to readyapi and there is a problem with ready api maven plugin...

all pom files were updated to use ready-api-maven-plugin : 

<pluginRepository>
        <id>smartbear-sweden-plugin-repository</id>
        <url>http://www.soapui.org/repository/maven2/</url>
</pluginRepository>
...
<groupId>com.smartbear</groupId>
<artifactId>ready-api-maven-plugin</artifactId>
    <version>1.4.0</version>
        <dependencies>
			<dependency>
				<groupId>com.oracle</groupId>
				<artifactId>ojdbc6</artifactId>
				<version>11.2.0.3</version>
			</dependency>
            <dependency>
                <groupId>soap.ahr.plugins</groupId>
                <artifactId>soap-ahr-plugin</artifactId>
                <version>0.6-plugin</version>
            </dependency>						
			<dependency>
				<groupId>org.reflections</groupId>
				<artifactId>reflections</artifactId>
				<version>0.9.9-RC1</version>
			</dependency>
			<dependency>
				<groupId>org.apache.poi</groupId>
				<artifactId>poi-ooxml</artifactId>
				<version>3.10-FINAL</version>
			<exclusions>
			<exclusion>
				<groupId>org.apache.xmlbeans</groupId>
				<artifactId>xmlbeans</artifactId>
				</exclusion>
				</exclusions> 
			</dependency>
		</dependencies>

But job fails with exception

 

[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] READY_API_TITLE
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NoSuchFieldError: READY_API_TITLE
	at com.smartbear.ready.cmd.runner.SoapUITestCaseRunner.<clinit>(SoapUITestCaseRunner.java:83)
	at com.eviware.soapui.maven2.TestMojo.execute(TestMojo.java:41)
	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
	at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182)
	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.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
	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 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:606)
	at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
	at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
	at hudson.maven.agent.Main.launch(Main.java:205)
	at hudson.maven.MavenBuilder.call(MavenBuilder.java:154)
	at hudson.maven.Maven2Builder.call(Maven2Builder.java:79)
	at hudson.maven.Maven2Builder.call(Maven2Builder.java:55)
	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
	at hudson.remoting.Request$2.run(Request.java:325)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 minutes 53 seconds
[INFO] Finished at: Fri Oct 16 15:19:08 CEST 2015
[INFO] Final Memory: 45M/962M

Is it a problem with plugin or we have incorrectly configured POM?

  • bzzup's avatar
    bzzup
    10 years ago

    Seems to be resolved by SmartBear team. 

    1. Repository should be <id>SmartBearPluginRepository</id> in the POM file.

    2. ReadyAPI plugin dependencies - just 

    <dependency>
	<groupId>com.oracle</groupId>
	<artifactId>ojdbc7</artifactId>
	<version>12.1.0.1</version>
</dependency>

    Thanks

     

    • bzzup's avatar
      bzzup
      Occasional Contributor
      10 years ago

      Not really... i'll explain our story from the beginning.

       

      The problem is - we already have hundreds of tests configured to work with SoapUI. We use hudson/jenkins to run them. Several weeks ago we decided to move to ReadyAPI, we've implemented new tests and then realized that we can't run them with SoapUI maven plugin as some features are supported by ReadyAPI only (i think). So we tried to update existing POM's and point them to ReadyAPI plugin instead. As a result - "No valid SoapUIPro license exists". OK, explainable. The next step was to install license on Jenkins slave - we did this and now we faced this new "READY_API_TITLE" problem.

      So, I believe we already have valid POMs with correct configuration and settings to run tests. The link you provided has totally different pom's and looks like this is not what we are looking for. 

      We have already raised support ticket around this, but it would be nice to know what causes our problem as many of community members would face the same problem sooner or later.

       

      Thanks, Andrei

      • TanyaYatskovska's avatar
        TanyaYatskovska
        SmartBear Alumni (Retired)
        10 years ago

        Hi Bzzup,

         

        I see that you’ve submitted the case to our Ready! API Support Team. I think our R&D team will need to investigate the behavior. Please share the solution with us.

         

Recent Discussions