-
Notifications
You must be signed in to change notification settings - Fork 22
Home
maven-soapui-extension-plugin adds new features and bug fixes to SmartBear soapui-pro-maven-plugin/soapui-maven-plugin.
In your pom replace
<plugins>
<plugin>
<groupId>com.smartbear.soapui</groupId>
<!-- If you want to use the pro version, put soapui-pro-maven-plugin -->
<artifactId>soapui-maven-plugin</artifactId>
<version>4.6.4</version>
...
</plugin>
...with
<plugins>
<plugin>
<groupId>com.github.redfish4ktc.soapui</groupId>
<!-- the plugin supports both OSS and PRO versions of SoapUI -->
<artifactId>maven-soapui-extension-plugin</artifactId>
<version>4.6.4.2</version>
...
</plugin>
...Note: for versions prior to 4.5.2, SmartBear plugin maven coordinates are eviware:maven-soapui-plugin (for pro, it was maven-soapui-pro-plugin)
For more information about plugin configuration, see
- the Goals page
- the Tips page
maven-soapui-extension-plugin is deployed to Maven Central Repository thanks to Sonatype OSS Repository Hosting Service but depends on SoapUI jars (that are not in Central). So you must be able to access dependencies from the SoapUI repository.
This means you need to add the soapui repository (or a proxy of it via your repository manager) to your plugin repository settings the same way it is required to use the SmartBear plugin implementation
See the official SoapUI maven plugins documentation about the repository configuration.
If you want to use development version of maven-soapui-extension-plugin (why? see Maven documentation), you need to declare the sonatype snapshot repository as plugin repository.
You can also browse https://oss.sonatype.org/content/repositories/snapshots/com/github/redfish4ktc/ and download plugins manually
Settings.xml configuration example
<profiles>
<profile>
<id>activate-sonatype-snapshots-as-plugin-repository</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<pluginRepositories>
<pluginRepository>
<id>sonatype-snapshots</id>
<url>http://oss.sonatype.org/content/repositories/snapshots</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
<releases>
<enabled>false</enabled>
</releases>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>Latest news are available on the project home page.
4.6.4.2 has just been released (see the changelog).
Next developments will focus on the 4.6.4.x line on
- new custom junit report for both OSS and PRO (see #42 and #56)
- mock-as-war support for all maven 2.2.1+ versions (see #70 and #121)
In parrallel, work on the 5.x line will also continue (currently paused because of dependency issues: javafx, missing dependencies in 5.1.x)
Latest version is now quite old. For the summer, I have been working to implement 5.x support but work is currently paused because of dependency issues (javafx, missing dependencies in 5.1.x)
So, I am currently focusing on a new version on the 4.6.4 line. As major new features, it will contain
- new custom junit report for both OSS and PRO (see #42 and #56)
- mock-as-war support for all maven 2.2.1+ versions (see #70 and #121)
Hope you will enjoy
4.6.4.2 (22-November-2014)
IMPROVEMENT
- #133 [build] Upgrade parent pom to version 7
TASK
- #108 [test-multi goal] add support for maven 2.2.1
4.6.4.1 (16-May-2014)
Various fixes and improvements. This is the first time a release contains external contribution thanks to thchittenden
FEATURE
- #50 [mock goal] add a parameter to generate Coverage HTML reports (PRO runner)
- #51 [mock goal] add a parameter to configure where Coverage HTML reports are generated (PRO runner)
IMPROVEMENT
- #123 [mock-as-war goal] add default value for the explodedWarDirectory parameter
BUG
- #68 "groovy.log" appender created once for every execution. This fix is based on contribution of thchittenden, see #69
- #122 [mock-as-war goal] NullPointerException when explodedWarDirectory or warFile is not set
TASK
- #47 Create custom SoapUIMockServiceRunner for OSS and PRO
- #91 Consider using assertj instead of fest-assert
- #118 Remove extra null checks in mojo implementation
4.6.4.0 (06-April-2014)
First version that supports SoapUI 4.6.4.
BUG
- #85 Issue with fetching dependencies
TASK
4.6.3.1 (27-March-2014)
New test-multi goal and improvements for the mock-as-war goal
FEATURE
- #77 [mock-as-war goal] add a runnerType parameter to choose the OSS generator
- #88 Add a test-multi goal: test multiple soapui projects easily
IMPROVEMENT
- #78 [mock-as-war goal] add a 'enableWebUI' parameter
- #104 [test-multi goal] add a parameter to have distinct output directory for each project execution
TASK
- #99 [mock-as-war goal] Create custom SoapUIMockAsWarGenerator for OSS
4.6.3.0 (03-January-2014)
First version that supports SoapUI 4.6.3.0.
TASK
- #96 Add support for 4.6.3 version
4.6.2.0 (03-January-2014)
First version that supports SoapUI 4.6.2.0.
BUG
- #95 [mock-as-war goal] generation fails in soapui 4.6.2 for PRO runner
TASK
- #93 Add support for 4.6.2 version
4.6.1.0 (22-December-2013)
First version that supports SoapUI 4.6.1.0.
BUG
- #87 [mock-as-war goal] generation fails in soapui 4.6.1
TASK
4.5.1.5 (23-November-2013)
This release contains a major feature: the new mock-as-war goal. It is currently in beta. Thanks for trying it and providing feedbacks.
This is also the last release with new features for the SoapUI 4.5.1 support. Next version will use SoapUI 4.6.1.
FEATURE
- #4 Add a mock-as-war goal
BUG
- #67 Plugin dependencies can't be resolved, when Eviware repository is cached/mirrored with Artifactory
- #76 Plugin version not correctly displayed on Ubuntu when using openjdk
TASK
- #66 Remove or skip integration tests using old versions of the smartbear plugin
- #75 4.5.2+ support: ban some dependencies
4.0.1.0 (30-July-2013)
This a the first release based on soapui 4.0.1. See the page dedicated to 4.0.1.x versions for more information.
BUG
- #9 workaround for "com.eviware.soapui.SoapUICore"'s signer information with maven-soapui-pro-plugin 4.0.1
- #17 add missing dependencies to maven-soapui-plugin 4.0.1
4.5.1.4 (24-April-2013)
FEATURE
- #39 [test goal] support overriding 'testsuite custom properties' with the PRO runner
- #45 [test goal] add a "junitHtmlReport" parameter (pro runner)
- #58 [test goal] add a way to configure the implementation of the report collector (OSS runner)
- #59 [test goal] add a way to configure the implementation of the report collector (PRO runner)
BUG
- #62 soapui maven plugin 4.5.1: missing guava dependency
TASK
- #46 Create a custom SoapUIProTestCaseRunner
4.5.1.3 (11-March-2013)
FEATURE
- #38 [test goal] add a parameter to override 'testsuite custom properties'
IMPROVEMENT
- #23 [mock goal] add a parameter to choose runner type
BUG
- #34 projectFile default value is always maven-soapui-extension-plugin-soapui-project.xml
4.5.1.2 (12-December-2012)
IMPROVEMENT
- #19 [mock goal] log files should be generated by default in a subdirectory of ${project.build.directory}
- #20 [mock goal] display the version of maven-soapui-extension-plugin
- #21 [mock goal] use maven logger when setting soapui property
- #22 [mock goal] skip running the mock service should log a message
- #28 [mock goal] do not log exception as a MojoFailureException is thrown
BUG
- #29 [test goal] log should display soapui 4.5.1 version instead of 4.5.1-SNAPSHOT
- #35 [mock goal] skip option does not work in pro and oss smartbear implementation (soapui 4.5.1)
TASK
- #33 Display build date and commit id when displaying plugin version
4.5.1.1 (28-November-2012)
- #14 [test goal] add a parameter to choose runner type
- #15 add a convert-project goal: convert a composite project into a standard project
- #16 [convert-project goal] convert a standard project into a composite project
- #25 [convert-project goal] log files should be generated by default in a subdirectory of ${project.build.directory}
- #27 [convert-project goal] display the version of maven-soapui-extension-plugin
4.5.1.0 (13-October-2012)
- #12 support soapui 4.5.1
4.5.0.0 (12-October-2012)
- #8 support soapui 4.5.0
4.0.0.2 (14-September-2012)
Note: even if #18 is marked as resolved in this version, #7 is fixed since 4.0.0.0 as maven-soapui-extension-plugin already depends on junit. In 4.0.0.2, we only upgrade junit version from 3.8.1 to 4.4
- #3 add a test-verify goal
- #10 [test goal] use maven logger when setting soapui property
- #13 [build] Add a way to have access to eviware repository
- #18 junit dependency still missing in maven-soapui-extension-plugin 4.0.0.1
4.0.0.1 (30-May-2012)
- #2 [test goal] do not display details of errors
- #5 [test goal] log files should be generated by default in a subdirectory of ${project.build.directory}
- #11 [test goal] display the version of maven-soapui-extension-plugin
4.0.0.0 (21-May-2012)
This is the first public version of the plugin (private versions were supporting SoapUI 3.6.1)
- #1 [test goal] skip running the tests should log a message
- #6 groovy.log destination directory should be configurable
- #7 add missing dependencies to maven-soapui-plugin 4.0.0
See the Development