cross platform. build 2000-05-12-10-M16. This worked OK in 5-6 builds, but broke in build 2000-05-08-09. Looks like it broke on Sunday, 5/7. 1. Go to http://jimbob/trigger3.html 2. Select a_fileop_filecopy from Acceptance Test Case menu. 3. Trigger. OK. 4. Check logfile and hard drive. Result: File copies from "Components" to "Program" folder. Either get -201 in logfile, or shows that filecopy.txt is appended to directory pathway. Expected: File should copy from "Components" to "Chrome". Note: I also tried these permutations: Program --> Chrome; Program --> Components. Both failed as well. logfile: ------------------------------------------------------------------------------- http://jimbob/jars/a_fileop_filecopy.xpi -- 05/12/2000 16:33:41 ------------------------------------------------------------------------------- Acceptance: a_fileop_filecopy ----------------------------- ** addFile returns = 0 [1/1] Installing: C:\Program Files\Netscape\Netscape 6\components\filecopy.txt Install completed successfully The File Copy part ------------------ ** fileSource pathway = C:\Program Files\Netscape\Netscape 6\components\filecopy.txt ** fileTarget pathway = C:\Program Files\Netscape\Netscape 6\chrome\ ** File.copy returns = 0 Install **FAILED** with error -201 Install **FAILED** with error -201 Finished Installation 05/12/2000 16:33:41

regression bug. Changed QA contact to depstein.

It's quite cleverly copying into the parent directory. Maybe he was worried about the target being a file instead of a directory, but it's supposed to be a directory. (hmm, maybe we should allow a Copy-to-new-name ability). I'll take this one since I was dinking around in here this weekend and now know what the problem is.

[nsbeta2+] since this seems to be part of the acceptance tests.

Reassigning to Don for load balancing

Fixed.

fixed cross-platform.