Feature request: Please consider adding a global log file location and removing the dependency on the bin/ directory being writeable by the user running ReadyAPI (or testrunner.sh, etc). Even better would be if you would support using a variable in the path, or simply relative paths, so that the ReadyAPI logs of one project could be placed under the project's working directory.
I'm not overly familiar with ReadyAPI but I imagine the ideal location in which to specify a log path would be in soapui-settings.xml.
Background (as per our forum post and support ticket):
We have installed in a system-wide location at /opt/SmartBear/ReadyAP-1.2.2, but unless we make the bin/ subdirectory of that path writeable by the user (not a good idea!) the software refuses to start.
Even giving write permissions to all of the individual log files that ReadyAPI expects to write to is insufficient. It requires write access to the bin/ subdirectory.
If I temporarily make bin/ writeable, I can launch the GUI, run tests, etc.
Even if installed into a user's home directory, we'd prefer for logs not to be created in the same dir as the binaries.
I have so far tried setting global properties as follows using the GUI:
Name:
soapui.logroot /home/user/soapui-workdir
user.dir /home/user/soapui-workdir
Neither of these worked when running our test suite, even after restarting the ReadyAPI GUI.
I have tried various combinations but ended up having to make our user the owner of the directory for ReadyAPI to even launch at all. I had considered editing soapui-log4j.xml but thought it was bad form to do so (and it's likely changes will be over-written next time we upgrade ReadyAPI).
I think many *nix systems administrators would be concerned about the fact that ReadyAPI requires write access to the binaries directory (not just the log files in it, but the whole directory).
