FULL PRODUCT VERSION :
java version "1.5.0_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-b05)
Java HotSpot(TM) Client VM (build 1.5.0_05-b05, mixed mode)

ADDITIONAL OS VERSION INFORMATION :
Windows 98

EXTRA RELEVANT SYSTEM CONFIGURATION :
1.5.0_05

A DESCRIPTION OF THE PROBLEM :
During installation, installer copies the same runtime .msi file to 3 different locations: one at C:\WINDOWS\Local Settings\Application Data\ , one at C:\WINDOWS\TEMP , one at C:\WINDOWS\TEMP\_is5163 , even before the actual unpacking begins. Furthermore, after installation, unpacked version of the .msi file is copied to C:\Program Files\Common Files\Sun . That makes the installation footprint extremely bloated, by copying everything to 3 locations at all stages. The installer should only copy the unpacked JRE once, to the destination directory.

Installer's behaviour aside, the whole JRE is contained inside the 11.5MB .msi file hidden inside Windows directory, yet the offline installer executable is 4.5MB bigger, which is too big to account for all the localized messages and unpacker used by installer. Besides, if JRE is distributed as an .msi package, it does not need an integrated unpacker anyway.

  To further complicate matters, if (un)installation is cancelled, an empty directory is littered inside C:\WINDOWS\TEMP directory. After uninstallation is completed, files in C:\WINDOWS\Local Settings\Application Data\ directory created at installation are not deleted.


STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
For installation bloat, just run the (un)installer and watch the contents in C:\WINDOWS\Local Settings\Application Data\ , C:\WINDOWS\TEMP , C:\Program Files\Common Files\Sun .


REPRODUCIBILITY :
This bug can be reproduced always.