Forum Discussion
redfish4ktc2
11 years agoSuper Contributor
Hi srahul101082 and SmartBear Support,
in addition, notice that as you are using version 4.6.1, the groovy-log.log file will still be stored in the base directory. This is because of a bug in SoapUI, the bug has been fixed in 5.0.0 (bug exist at least from 3.6.1 to 4.6.4)
If you can not ugrade to 5.0.0, you have the following workarounds
* define a custom log4j configuration file in the base directory or in a specific location (need extra conf)
* use maven-soapui-extension-plugin (my custom implementation of the plugin, not supported by SmartBear) which has not the bug for SoapUI 4.6.1 and which also store all log files in ${project.build.directory}/soapui/logs by default
You can find detailled information about log configuration for both SmartBear and my implementation here: https://github.com/redfish4ktc/maven-so ... figuration
in addition, notice that as you are using version 4.6.1, the groovy-log.log file will still be stored in the base directory. This is because of a bug in SoapUI, the bug has been fixed in 5.0.0 (bug exist at least from 3.6.1 to 4.6.4)
If you can not ugrade to 5.0.0, you have the following workarounds
* define a custom log4j configuration file in the base directory or in a specific location (need extra conf)
* use maven-soapui-extension-plugin (my custom implementation of the plugin, not supported by SmartBear) which has not the bug for SoapUI 4.6.1 and which also store all log files in ${project.build.directory}/soapui/logs by default
You can find detailled information about log configuration for both SmartBear and my implementation here: https://github.com/redfish4ktc/maven-so ... figuration
Related Content
- 2 years ago
- 8 years ago
- 8 years ago
Recent Discussions
- 18 days ago