I think I may have fixed this by upgrading the soapUi version to 2.7.0.
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://maven.apache.org/POM/4.0.0"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>groupId</groupId>
<artifactId>artifactId</artifactId>
<version>1.0-SNAPSHOT</version>
<properties>
<unpackdir>${project.build.directory}/resources/testdata</unpackdir>
<projectFile>CompositeProjectDir</projectFile>
<outputDirectory>${project.build.directory}/test-reports</outputDirectory>
<environment>QA</environment>
<soapui.home>C:\Program Files\SmartBear\ReadyAPI-2.1.0</soapui.home>
<testSuite>UmlerLookUp</testSuite>
</properties>
<build>
<plugins>
<plugin>
<groupId>com.smartbear</groupId>
<artifactId>ready-api-maven-plugin</artifactId>
<version>2.1.0</version>
<configuration>
<readyApiProperties>
<soapui.home>${soapui.home}</soapui.home>
</readyApiProperties>
<testFailIgnore>true</testFailIgnore>
<outputFolder>${outputDirectory}</outputFolder>
<junitReport>true</junitReport>
<exportAll>false</exportAll>
<printReport>false</printReport>
<projectProperties>
<environment>${environment}</environment>
</projectProperties>
</configuration>
<executions>
<execution>
<id>CrmsSoapTests</id>
<phase>test</phase>
<goals>
<goal>test</goal>
</goals>
<configuration>
<projectFile>${projectFile}</projectFile>
<!-- <testSuite>${testSuite}</testSuite>-->
<!-- <junitReport>true</junitReport>-->
<!-- <exportAll>false</exportAll>-->
<!-- <printReport>false</printReport>-->
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>com.oracle</groupId>
<artifactId>ojdbc8</artifactId>
<version>12.2.0.1</version>
</dependency>
<dependency>
<groupId>com.smartbear</groupId>
<artifactId>ready-api-soapui</artifactId>
<version>2.1.0</version>
</dependency>
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
<version>1.2.3</version>
</dependency>
</dependencies>
</project>
Sorry, I wasn't clear, please provide us with the pom.xml file for which you get this stack trace.
Do it have these properties?
<properties>
<unpackdir>${project.build.directory}/resources/testdata</unpackdir>
<projectFile>CompositeProjectDir</projectFile>
<outputDirectory>${project.build.directory}/test-reports</outputDirectory>
<environment>QA</environment>
<soapui.home>C:\Program Files\SmartBear\ReadyAPI-2.1.0</soapui.home>
</properties>
Also, I see that you use ReadyAPI 2.1.0, please try the latest version of ReadyAPI which is 2.7.0 now:
That is the pom.xml
${project.build.directory} <- this is the directory that maven uses to build the project. It is a system variable.
I cannot use Ready-API version 2.7.0 because it throws a bunch of null pointer exceptions when I try to launch it. And is completely unusable in our environment. I have a seperate support case for that issue.
Hi,
The pom.xml file seems to be OK if instead of CompositeProjectDirectory you have something like this:
D:/ReadyAPI Projects/TEST-readyapi-project
The "java.lang.ClassNotFoundException: com.sun.jdi.request.EventRequest" exception which you posted in the first message in this thread is related to an Event. To further troubleshoot the issue, we will need your project file.
I see that you have already created a support case about this issue. Please continue working on this issue with my colleague in the corresponding Support case.
I think I may have fixed this by upgrading the soapUi version to 2.7.0.
