Hi,
I have face the same problem. So 4 solutions :
1 - use a repository between you and internet (nexus, artifactory...) with the patched soapui version. The free opensource version allow you to do that.
2 - add a ant plugin task with maven that move this file to his desired location after the test soapui are done
3 - use soapui-3.6.2-SNAPSHOT. This bug was already corrected :
<appender name="GLOBAL_GROOVY_LOG" class="org.apache.log4j.FileAppender">
<errorHandler class="org.apache.log4j.helpers.OnlyOnceErrorHandler"/>
<param name="File" value="${soapui.logroot}global-groovy.log"/>
4 - a) don't give a damn of the global-groovy.log. location. It will not add supervalue & consume too much time.(see : pareto method) Problem: it will not be erased in the clean phase.
b) Solution: use the clean plugin to remove it during the clean phase.
I'm using right now solution 4 a). Solution 3 introduce new bugs in others place (registering jdbcDriver, proxy not working...) I'm using 3.5.1 under windows and linux devian.
Omar
