United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-4892335 : PIT: Java cup icon in Windows Control Panel and Jaws desktop icon not updated

Details
Type:
Bug
Submit Date:
2003-07-17
Status:
Closed
Updated Date:
2003-10-03
Project Name:
JDK
Resolved Date:
2003-10-03
Component:
install
OS:
windows_nt,windows_2000
Sub-Component:
install
CPU:
x86,generic
Priority:
P4
Resolution:
Won't Fix
Affected Versions:
1.4.2_01,1.4.2_02
Fixed Versions:

Related Reports
Duplicate:

Sub Tasks

Description
j2re1.4.2_01
All Windows platforms

Java cup icon in Windows Control Panel and Jaws desktop icon not updated with the new one.

Steps to reproduce:
- install j2re1.4.2_01
- check Java cup icon in Windows Control Panel and Jaws desktop

                                    

Comments
EVALUATION

Summary:
1.) this is all based on a bug in windows.  If you replace a file containing an ico file with another file of the same name containing a different ico file.  Windows will display the old icon (from some internal cache we know not where) for some
time afterwards.  Eventually it with then start displaying the new version.  Re-booting dosnt fix the problem.
2.) To fix the problem we would need to change the name of the file containing the ico .  For webstart this could be done, since the file is just JavaCup.ico, and is only referenced in less than a half a dozen places.  For plugin the file is
jpicpl32.cpl . and is placed in the windows directory, so it would be a lot harder to change the name and fix the installer to then do the right thing.

options;
1.) Do nothing - problem is only showing older icon on systems that already had the old files installed, and it fixes itself in time.
2.) Fix only Java Web Start, and leave the problem for plugin control panel. - need respin with fix to do.
3.) Fix both Plugin and Webstart - significant plugin and installer changes very late in cycle.

###@###.###
2003-07-17

Fix this bug will cause side-effect plus there won't be many user complaining about it. So we won't fix it.


Based on the comment from Stanley, we have to wait to see whether this will affect 1.4.2_01 release. If it does, we need to fix it.

###@###.### 2003-07-26
###@###.### 2003-10-03
                                     
2003-07-26



Hardware and Software, Engineered to Work Together