Forum Discussion
redfish4ktc2
12 years agoSuper Contributor
apattanayak the -e option does not help
about the maven-soapui-extension-plugin version: this is not documented, but versions always follow <soapui version>.<increment>. So 4.6.3.1 uses SoapUI 4.6.3. So to check SmartBear implementation, you should try the 4.6.3 version
anyway, you could also try soapui-pro-maven-plugin 4.6.2 and 4.6.3 to know when the problem has been introduced.
I have another question, does you manage your project with SoapUI free? you could try with soapui-maven-plugin (free version) and maven-soapui-extension-plugin with the runnerType parameter set to OSS to check if you still have the issue.
The problem may only occur with the pro version and these tests will confirm this
Last thing, when you use maven-soapui-extension-plugin, the logs suggest that you use the test goal instead of the test-multi. Only the test-multi will allow you to run serveral projet by providing directories with include/exclude to find projects
about the maven-soapui-extension-plugin version: this is not documented, but versions always follow <soapui version>.<increment>. So 4.6.3.1 uses SoapUI 4.6.3. So to check SmartBear implementation, you should try the 4.6.3 version
anyway, you could also try soapui-pro-maven-plugin 4.6.2 and 4.6.3 to know when the problem has been introduced.
I have another question, does you manage your project with SoapUI free? you could try with soapui-maven-plugin (free version) and maven-soapui-extension-plugin with the runnerType parameter set to OSS to check if you still have the issue.
The problem may only occur with the pro version and these tests will confirm this
Last thing, when you use maven-soapui-extension-plugin, the logs suggest that you use the test goal instead of the test-multi. Only the test-multi will allow you to run serveral projet by providing directories with include/exclude to find projects