New 4.5.0 maven-soapui-plugin missing class
Works fine with 4.5.0-SNAPSHOT but fails with 4.5.0. mavenExecutionResult exceptions not empty message : Failed to execute goal eviware:maven-soapui-plugin:4.5.0:test (iregression) on project mave...
Forum Discussion
djangofan
Thanks for your feedback
about the missing dependency
If you want to make your build work out of the box, add directly the dependency to you plugin configuration in the pom as you did for the mysql dependency
The only issue with this is that you will have to add the dependency in all pom which use the soapui plugin
You can also use the maven soapui pro plugin because the dependency is not missing and also give a try to https://github.com/redfish4ktc/maven-so ... on-plugin/ which fixes some other issues
About the groupId, yes it is bad
Actually, SmartBear has used for a long time maven 1 build and use non standard groupId for maven 2 dependencies.
The build now use maven 3 so we can expect this to be progressively fixed.
I've started to fix this but the work is still in progress: see https://github.com/redfish4ktc/soapui/t ... es-groupId
Thanks for your feedback
about the missing dependency
If you want to make your build work out of the box, add directly the dependency to you plugin configuration in the pom as you did for the mysql dependency
<plugin>
<groupId>eviware</groupId>
<artifactId>maven-soapui-plugin</artifactId>
<version>4.5.0</version>
<dependencies>
<dependency>
<groupId>mysql</groupId>
<artifactId>mysql-connector-java</artifactId>
<version>5.1.6</version>
</dependency>
<dependency>
<groupId>fife</groupId>
<artifactId>rsyntaxtextarea</artifactId>
<version>2.0.1</version>
</dependency>
</dependencies>
<configuration>....
The only issue with this is that you will have to add the dependency in all pom which use the soapui plugin
You can also use the maven soapui pro plugin because the dependency is not missing and also give a try to https://github.com/redfish4ktc/maven-so ... on-plugin/ which fixes some other issues
About the groupId, yes it is bad
Actually, SmartBear has used for a long time maven 1 build and use non standard groupId for maven 2 dependencies.
The build now use maven 3 so we can expect this to be progressively fixed.
I've started to fix this but the work is still in progress: see https://github.com/redfish4ktc/soapui/t ... es-groupId