This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | uninstaller fails in bundled jdk on RHAS4.0 | ||
---|---|---|---|
Product: | installer | Reporter: | Jan Lana <jl149544> |
Component: | JDK bundle | Assignee: | mslama <mslama> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | Keywords: | RELNOTE |
Priority: | P2 | ||
Version: | 5.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Output of 'sh -x uninstaller 2>log' |
Description
Jan Lana
2007-03-05 16:21:08 UTC
Created attachment 39175 [details]
Output of 'sh -x uninstaller 2>log'
I tried /home/tester/jdk1.6.0_01/bin/java -jar uninstall.jar and it works. Interesting, because ./uninstaller -is:javahome /home/tester/jdk1.6.0_01 fails. Problem is that bundle uninstaller ignores -is:javahome command line option. Uninstaller of standalone NB IDE works fine. It is InstallShield problem. I do not know if we will be able to patch uninstaller launcher. It is common issue not only for bundle uninstaller. On Linux/Solaris uinstaller ignores command line option -is:javahome. Unfortunately we are not able to fix this issue. Workaround is to run installer directly using 'java -jar uninstall.jar' if uinstaller launcher fails to locate JDK. It is more complicated: Uninstaller launcher first tries to search JDK using predefined rules. If it fails then it can use -is:javahome. Installer launcher behaves differently. Anyway whole algorithm is complicated and is out of our hands. It is InstallShield code. So workaround still applies: If uninstaller launcher fails to locate JDK try -is:javahome. If even -is:javahome fails run uninstaller directly with 'java -jar uninstall.jar'. I even tried to set all uninstaller options in installer project for bundle uninstaller launcher to the same values as for standalone IDE uninstaller launcher but behavior did not change. We will have new installer for jdkbundle NB 6.0 + JDK X so this issue will be fixed in 6.0. |