Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 0.1
-
Fix Version/s: 0.2
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
This is a major problem ![]()
I set the working directory to my source path (as I wasn't sure quite what it did) - and when I stopped the server Cargo deleted all my source.
Traced the problem down to DefaultContainer.cleanWorkingDirectory().
If this is what it's meant to do, I'd put a HUGE warning on the doco and everywhere to ensure that users don't set the working directory to a directory that already contains files before Cargo starts.
Cargo now cleans up working directory only if there is a cargo timestamp file and a cargo timestamp file is only created in empty directories.