I am now of the opinion that this is a bug within the soapUI plugin.
The plugin is run for the int testing of the service2, but doenst shut down when that round of int testing has finished, it is then started again for service1 when service1 makes calls to service2 it looks like these are mocked correctly. However when service2 makes calls to the common service3 it looks like the calls are routed to the mock created for service1.
This is shown by the fact that the mocks for service2 do not contain the same end points as for service1, and both mocks use different port numbers for the mocking of service3. when the missing end points are added to service2 mock all tests pass.
The defect is either that the soapUI plugin is unable to shut itself down after the end of the build phase for service2, or that soapUI's internal routing is unable/fails to determin the correct mock based upon the port address.
Of course I could be missing a configuration option.
Is there a way to stop/shutdown/kill the soapUI plugin at the end of the build cycle so that when the pom is activated for service1 there is no soapUI run?
