maven-soapui-plugin doesnt shutdown at end of build
System details
Java 1.6
Ubuntu 10.04
Maven 3
maven-soapui-plugin 4.0.1
Given a maven project with two nested multi module projects.
Each of the nested projects contains a webservice project. Service1 depends upon the Services of Service2, and both Service1 and Service2 depend on ExtService.
Each nested webservice project has its own set of integration tests which make use of maven-soapui-plugin to mock out ExtService, and Service1 has additional mocking for Service2.
Service1 depends on methodX from ExtService while Service2 has no such dependency, so the mocks configured for Service1 have ExtService.methodX while the mocks for Service2 do not.
When mvn clean install is ran for each individual nested project all tests pass as expected and build.
However when we run mvn clean install on the parent project we see test failures in Service1 (note due to the fact that Service1 depends on Service2 it is the second project to be built).
We see an error stating that we have a missing service.
Initially as both Service1 and Service2 required ExtService the mocks where configured for the same port, changing the port for one instance of ExtService didnt not help, however when observing the open ports I noticed that the mock service for Service2 build phase was still open during the build phase of Service1.
This indicates that maven-soapui-plugin is not shutting down during the build phase, nor it appears am I able to map a shutdown goal to a life cycle phase.
Java 1.6
Ubuntu 10.04
Maven 3
maven-soapui-plugin 4.0.1
Given a maven project with two nested multi module projects.
Each of the nested projects contains a webservice project. Service1 depends upon the Services of Service2, and both Service1 and Service2 depend on ExtService.
Each nested webservice project has its own set of integration tests which make use of maven-soapui-plugin to mock out ExtService, and Service1 has additional mocking for Service2.
Service1 depends on methodX from ExtService while Service2 has no such dependency, so the mocks configured for Service1 have ExtService.methodX while the mocks for Service2 do not.
When mvn clean install is ran for each individual nested project all tests pass as expected and build.
However when we run mvn clean install on the parent project we see test failures in Service1 (note due to the fact that Service1 depends on Service2 it is the second project to be built).
We see an error stating that we have a missing service.
Initially as both Service1 and Service2 required ExtService the mocks where configured for the same port, changing the port for one instance of ExtService didnt not help, however when observing the open ports I noticed that the mock service for Service2 build phase was still open during the build phase of Service1.
This indicates that maven-soapui-plugin is not shutting down during the build phase, nor it appears am I able to map a shutdown goal to a life cycle phase.