| << Back to previous view |
|
[QB-219] QuickBuild should not attempt to delete temporal directory at startup
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Robin Shen | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
From PMEase forum: #1: I did this, and I was able to direct my quickbuild to use d:\temp. However, when I started QuickBuild, it immediately deleted and recreated the d:\temp directory, hosing another task that was also using the same temp directory. This is not cool. Workaround is to create a d:\temp\quickbuild directory and point quickbuild to use it instead. #2: If another process has files open in the d:\temp directory as described above, QuickBuild fails to delete the directory and goes into a hosed state. On my test system, I am using HSQLDB, which puts files in %TEMP%, which points to the same directory to which I pointed QuickBuild to use as its temp directory. QuickBuild has to be running before I can change the setting, and I can't start QuickBuild because it depends on HSQLDB. I had to reinstall QuickBuild to get out of this scenario. |