-
Notifications
You must be signed in to change notification settings - Fork 22
"groovy.log" appender created once for every execution #68
Comments
@thchittenden good catch. I didn't notice this. |
PR #69 provides a fix for both test and mock goals. Will be ok as 1st implementation. |
Just realize that the problem can be reproduce by running integration test |
A user complained about this in the Soapui forum, see this post |
Would it be possible to have one global-groovy.log (and 2 other log files) per module ? In fact with multi-module maven project there is only one directory soapui/logs created. It would be nice to have one per module. The first module using soapui mock creates the log directory and then all other module are logging in it. It's difficult to analyse logs |
@acommuni thanks for your feedback |
It's done. Thank you. |
ok, new issue is #98 |
When implementing this fix, also notifty users in the SoapUI forum |
This is especially annoying when running with the |
Add tests for both our plugin and the SmartBear implementation. 2 projects are runned. For the 2nd, groovy logs are appended twice.
Add tests for both our plugin and the SmartBear implementation. 2 projects are runned. For the 2nd, groovy logs are appended twice.
Merged into |
With every execution of the plugin a new ConsoleAppender is created for the "groovy.log" class so after 5 executions of the plugin each message from a groovy script is logged 5 times.
If the initGroovyLog method from AbstractSoapUIRunner were stubbed in SoapUI(Pro)ExtensionTestCaseRunner and the console appender configured in soapui-log4j.xml I think that would fix it.
The text was updated successfully, but these errors were encountered: