-
Bug
-
Resolution: Fixed
-
P3
-
7
-
b139
-
generic
-
generic
-
Not verified
This bug is to follow up against CR http://monaco.sfbay.sun.com/detail.jsf?cr=7014289
Seems javacpl didn't get the expected manifest. Javaws is ok.
Tested build: jdk7 b135-pit
http://rehudson.sfbay.sun.com/hudsonws/deploypit/bundles/windows-i586/b255-2011-03-16_50/
Tested OS:Win xp sp3 32bit
Steps to reproduce
1.Install InspectEXE 3.1
2.right click javacpl.exe and select Properties - Manifest.You will see the manifest setting.
3.as a result there should be DPIAWARE setting just like the one in javaws. Now it may get a default manifest without it.
Seems javacpl didn't get the expected manifest. Javaws is ok.
Tested build: jdk7 b135-pit
http://rehudson.sfbay.sun.com/hudsonws/deploypit/bundles/windows-i586/b255-2011-03-16_50/
Tested OS:Win xp sp3 32bit
Steps to reproduce
1.Install InspectEXE 3.1
2.right click javacpl.exe and select Properties - Manifest.You will see the manifest setting.
3.as a result there should be DPIAWARE setting just like the one in javaws. Now it may get a default manifest without it.
- relates to
-
JDK-7014289 deployment windows exe files need to have appropriate manifests
-
- Closed
-