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.
I downloaded NetBeans 5.0 beta with AS8.1 from java.sun.com and tried to install it on my laptop which has a fresh Solaris 10 installation. The installation quits after the "Verifying JVM" step: Initializing InstallShield Wizard........ Verifying JVM. bash-3.00$ bash-3.00$ java -version java version "1.5.0_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08) Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode) bash-3.00$
I am not able to reproduce it. I've tried to install it on same configuration and everything done well. Please try to use other JDK. You can run the installer with this switch: <installer> -is:javahome <path_to_jdk>
Reporter, can you run installer with option -is:log logfile and attach the log file? Thanks.
I'm able to reproduce this with daily build - 200510111800 - on sol10-sparc (s2). installer log is attached.
Created attachment 25853 [details] installer log
forgot to say that JAVA_HOME environment property was set to /usr/java (jdk 1.5.0_03)
same result for nb+sjsas inst. bundle
I reported it to InstallShield as bug. I found problem is caused by presence of /bin in PATH. It is duplicate as /bin is link to /usr/bin. When /bin is in PATH JVM resolution in installer launcher fails. Workaround is either to remove /bin from PATH (it is not necessary as I said above) or use command line switch -is:javahome <Path to JDK>. No need to set JAVA_HOME to reproduce this problem.
I forgot to say I placed /bin as first item in PATH. Order of items could be important.
I am puzzled by the fact that you simply closed this report. I would like to remind you that this problem occurs on a vanilla Solaris 10 installation. Do you actually suggest that in order to install NetBeans, a user (who might not even have root access) should go ahead and remove the /bin symlink, which is there by default in Solaris? I would feel very uneasy doing such a thing, not knowing what the consequences would be. Also, how on earth would a user know to proceed with ANY of the two workarounds you suggest? The installer simply *exits*. No error message. How can the user know the problem is the /bin symlink? And there is no hint to run with -is:javahome either. This is bad user experience. People will not fiddle with this for a long time, they will go ahead and download Eclipse instead. I guess you're happy with that?
Sorry, I didn't mean removing the symlink, but moving /bin from PATH. From where should the user get that idea? And why is the symlink a problem? The installer should be able to figure it out - any other java program can easily be run simply invoking 'java <program>', so why not the installer?
I found simple workaround (Check of /bin is omitted in launcher.)
Fixed. Michal please verify in new installer builds produced by RE. Today it should be integrated by RE to build environment. Discuss with RE when it will be ready. Thanks.
Verified