Another temporary solution I am playing with is to have multiple executions of the plugin and then just connect it to a phase of the main lifecycle. This makes it easier to automate. I am also adding my soapUI test results in with my regular JUnit test results by adding them into the surefire-reports folder.
For example:
<build>
<plugins>
...
<plugin>
<groupId>eviware</groupId>
<artifactId>maven-soapui-plugin</artifactId>
<version>3.5.1</version>
<configuration>
<outputFolder>target/surefire-reports/</outputFolder>
<printReport>true</printReport>
<junitReport>true</junitReport>
<testFailIgnore>true</testFailIgnore>
</configuration>
<executions>
<execution>
<phase>test</phase>
<id>soapui-tests1</id>
<configuration>
<projectFile>${basedir}/src/test/soapui/some-soapui-project.xml</projectFile>
</configuration>
<goals>
<goal>test</goal>
</goals>
</execution>
<execution>
<phase>test</phase>
<id>soapui-tests2</id>
<configuration>
<projectFile>${basedir}/src/test/soapui/some-other-soapui-project.xml</projectFile>
</configuration>
<goals>
<goal>test</goal>
</goals>
</execution>
</executions>
</plugin>
...
</plugins>
</build>
