redfish4ktc/maven-soapui-extension-plugin — Issue #5: log files should be generated by default in a subdirectory of ${project.build.directory}
Author: redfish4ktc
Created: 2012-02-22 20:33:30+00:00
State: open

#### The problem

Currently, this is possible to configure the destination directory for almost all log files by doing the following (the trailing / is a mandatory in the log output directory)

```xml

eviware
maven-soapui-plugin
4.0.1

soapui.logroot
${project.build.directory}/soapui/logs/

```

But this should be done in all projects that used the soapui maven plugin.
Also, this does not work for the groovy.log file (at least from 3.5.1 version). An issue is still opened for this (see http://sourceforge.net/tracker/index.php?func=detail&aid=2882169&group_id=136013&atid=737766) even if it seemed to have been fixed in the unreleased 3.6.2 version.
There is a workaround but again, you must do it in all projects (use a specific log4j configuration file)

* comments in http://sourceforge.net/tracker/index.php?func=detail&aid=2882169&group_id=136013&atid=737766
* http://www.soapui.org/forum/viewtopic.php?f=5&t=6949

#### The proposed solution
As suggested in the SF issue

* the groovy.log file should be generated along with the other log files
* all log files should be generated in ${project.build.directory}/soapui/logs/ by default to avoid configuring this in all maven projects