Forum Discussion
bmgriner
15 years agoFrequent Contributor
yves42,
I actually found that having a parent pom with sub projects each with pom files that defined SoapUI project info turned into quite a mess. The solution that I found the best was to add multiple executions of the plugin while changing the project location.
They you call mvn integration-test and it will run both projects.
I actually found that having a parent pom with sub projects each with pom files that defined SoapUI project info turned into quite a mess. The solution that I found the best was to add multiple executions of the plugin while changing the project location.
...
<plugin>
<groupId>eviware</groupId>
<artifactId>maven-soapui-plugin</artifactId>
<executions>
<execution>
<phase>integration-test</phase>
<id>[SomeID]</id>
<configuration>
<projectFile>${pom.basedir}/src/test/soapui/[Some]-soapui-project.xml</projectFile>
</configuration>
<goals>
<goal>test</goal>
</goals>
</execution>
<execution>
<phase>integration-test</phase>
<id>[SomeOtherID]</id>
<configuration>
<projectFile>${pom.basedir}/src/test/soapui/[SomeOther]-soapui-project.xml</projectFile>
</configuration>
<goals>
<goal>test</goal>
</goals>
</execution>
</executions>
</plugin>
...
</build>
They you call mvn integration-test and it will run both projects.