Build: 4/28/99 Engineering build 1. Trigger http://jimbob/jars/addsubcomp_3files.jar 2. A directory named "null/regname" is created in the Installed directory with three files (absolute_SmartUpdate.txt, NULL_SmartUpdate.txt, and relative_SmartUpdate.txt) 3. Trigger this same jar file again RESULT: Copies of the files are found in the Temp directory with names like xpinstall-1.txt, xpinstall-2.txt, etc. The Install.log indicates that the files have been replaced, but the time stamp on the files says this is not true. Also, a copy of the jar file is copied to the Temp directory with each trigger. EXPECTED RESULT: No duplicate files (ie xpinstall-1.txt, etc.) are found in the Temp directory. Jar files are not copied to the Temp directory. Triggering the same jar should replace the files as the log file describes because from the installscript I am forcing the AddSubcomponent regardless of version info. NOTE: This bug report was communicated previously by email. We should now track this bug in this record.

Changing QA Contact from Grace to Jimmy.

reasign to dveditz, and setting setting target milestone to M11

This bug is already fixed. We no longer extract data files into temp directory. They're extracted into the destination directory (where files should be installed), and they get cleaned up afterwards.

Build 8/27/99 I am still finding JAR files in the Temp directory. I don't know if we extract at the destination directory or not.

Jimmy, this bug is already fixed. We no longer extract Jar data files (in this case, xpinstall-1.txt, xpinstall-2.txt...) into temp directory, and not cleaning them up afterwards. There is a different bug 12166 for cleaning up actual JAR/XPI files.

Good enough. Bug 12166 will track the JAR files remaining in Temp. The "xpinstall-1.txt"-type files are no longer present. Marking Verified.

Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall Engine