Today, I found that all the files will be deleted after executing the program copy. At that time, I checked the program feeling weird. I started suspected to be SWT (because this is the first trial to try to exit the destruction of the resource "all copies It is destroyed as a resource. After coming back at night, I will continue to do track. I finally discovered the problem. Check the file before copying the file. If there is a logic that deletes the file, this logic itself has no problem, the problem is called File.deleteonexist. ) after carefully reading the API documentation found Requests that the file or directory denoted by this abstract pathname be deleted when the virtual machine terminates. Deletion will be attempted only for normal termination of the virtual machine, as defined by the Java Language Specification. Once deletion has been requested, it is not possible to cancel the request This method should therefore be used with care Note:.. this method should not be used for file-locking, as the resulting protocol can not be made to work reliably The FileLock facility should. That is to say, this method will make a file delete operation when the JVM is destroyed, and specifically, this method does not use it in the case of the file lock. At this time, I suddenly deleted the resource when I was destroyed when I was destroyed when I was destroyed in SWT (at this time, and I was verified again. " Finally, in order not to affect the logic to change this method to file.delete (), I realized that I realized the importance of a programmer for the basic API's proficiency. Take this with everyone, I hope everyone should not like me. Since there is no time to do unit test, it is ignored at the beginning.
