"groovy.log" appender created once for every execution
thchittenden opened this issue · comments
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.
@thchittenden good catch. I didn't notice this.
Feel free to provide a pull request to fix this in this project (I won't have time to work on this before several weeks) or directly in the SmartBear/soapui repository
PR #69 provides a fix for both test and mock goals. Will be ok as 1st implementation.
Next we would have to fix this on other goals (in custom runners or directly in AbstractSoapUIRunner to avoid duplication accross runners)
Just realize that the problem can be reproduce by running integration test test-verify_goal/sucessfull_and_failing_projects
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
This is a nice idea, I have also faced this issue.
Could you create a new issue about this subject because the current issue is not related to your problem (I will also update the documentation to explain the current limitation you have noticed)?
It's done. Thank you.
When implementing this fix, also notifty users in the SoapUI forum
This is especially annoying when running with the test-multi goal as in this case, several projects are runned.
This should be fixed in 4.6.4.1
Merged into master, this issue is fixed in 4.6.4.1