]
Nick Boldt commented on JBDS-1918:
----------------------------------
Committed to trunk based on locally built and tested installer.
Should we roll this out to the 4.1.1.GA and 3.3.0.M4 installer builds too?
Uninstaller shortcut launches JBDS instead of izpack uninstaller
----------------------------------------------------------------
Key: JBDS-1918
URL:
https://issues.jboss.org/browse/JBDS-1918
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: installer
Affects Versions: 4.1.1.GA, 5.0.0.M4
Environment: Win7 64-bit w/ JDK 6u25 32-bit
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Critical
Fix For: 4.1.1.GA, 5.0.0.M4
Steps to repro:
1. Install JBDS 4.1.1.CR2 (GA) or JBDS 5.0.0.M4 from any of these:
{code}
jbdevstudio-product-win32-5.0.0.v201110271830R-H42-M4.jar
jbdevstudio-product-eap-win32-5.0.0.v201110271830R-H42-M4.jar
jbdevstudio-product-win32-4.1.1.v201110271900R-H748-GA.jar
jbdevstudio-product-eap-win32-4.1.1.v201110271900R-H748-GA.jar
{code}
2. Next, try to uninstall from the menu item, which tries to run this:
{code}
C:\Users\nboldt\jbdevstudio-product-win32-4.1.1.v201110271900R-H748-GA\studio\jbdevstudio.exe
-Dizpack.mode=privileged -jar
"C:\Users\nboldt\jbdevstudio-product-win32-4.1.1.v201110271900R-H748-GA/Uninstaller\uninstaller.jar"
{code}
3. The result is that JBDS is launched -- seems the flags are simply ignored.
4. Suggest that instead, we run this w/ the Run in folder left blank instead of set to
the Uninstaller folder:
{code}
"C:\Users\nboldt\jbdevstudio-product-win32-4.1.1.v201110271900R-H748-GA/Uninstaller\uninstaller.jar"
or
java -jar
"C:\Users\nboldt\jbdevstudio-product-win32-4.1.1.v201110271900R-H748-GA/Uninstaller\uninstaller.jar"
{code}
That way the resulting leftovers are minimal -- if we Run In the Uninstaller folder, it
won't be deleted even if the [x] Force removal box is checked. Note too that with that
box checked, the install folder, eg., "C:\Users\nboldt\jbdevstudio", is NOT
deleted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: