-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: C:\Temp\RoundhousE may not exist #7
Comments
Even a bigger problem with the c:\temp\roundhouse\roundhouse.changes.log is that when RoundhousE is executed on a buildserver for multiple projects at the same time, then one of the builds fail. Because the logging file is in use by another process. A better solution would be to make the output folder required, and always log there, instead of first logging to c:\temp and then copying the file. |
Yep - to do that I need to actually set up logging configuration that Rob http://devlicio.us/blogs/rob_reynolds On Thu, Jun 9, 2011 at 4:08 PM, PascalMestdach <
|
And that would be a better solution. I am not a fan of having it go one place and then moving it somewhere. Perhaps I can grab the logger and point it to the correct directory to ease the configuration pain. |
Yes, that would solve it. And maybe give the outputfolder a default to c:\temp\roundhouse so that it's no breaking change? |
Actually no one knows/cares about that folder. It started as a dropping point for the log prior to moving it to the change drop folder. It was meant to be temporary at the time it was added... |
Fixed in 9250541 |
Writing the log file out will fail if it can't reach the folder above.
The text was updated successfully, but these errors were encountered: