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.
e.g. I have installed j2sdk 1.3.1_02, but I want to specify s different JDK e.g. 1.4.0
Why do you want to specify another than installed jdk? Does it make sense. If you want to specify e.g. JDK 1.4.0 then you should install JDK1.4.0.
It have sence. E.g. on my solaris box is installed J2SDK. The startup script can be executed, if you have setted env variable $JDK_HOME, but this env variable doesn't exit by default ... so at minimum I MUST specify java directory ... and the best is in the installer. Everyone can use more then last release of the JDK (for different applications), so why not eneble choose of the JDK ??? If I'm completly wrong, please let me know.
I think that having installation panel where J2SE can be specified is pretty useful. User can have installed several J2SE of different version. Asking user to specify one for "exactly this" IDE installation can help user to decide and not to be surprised when IDE is started or cannot be started.
You are asking for new functionality, changing to enhancement. We can reconsider it for next release(s). Please, read also the specification for NetBeans 3.4 Installer: http://ui.netbeans.org/docs/hi/install_support/InstallersUIS.html
Hi Jirka, I discussed this with Jan Chalupa and we decide that this is bug and not enhancement, so reopen it as a bug. Finaly I read th installer specification befor I fill this issue for the first time ;-\
I don't understand why user should be asked to specify which jdk to use for running NB at install time. Without properly installed jdk she can't run installer at all. We also declare that NB runs on jdk1.3 and 1.4, thus if any of them is installed NB should run without problems (installer should not be used as workaround for jdk dependent bugs). For our users NB is like any other java application which runs on installed jdk. I think this is not a bug and definitely not P2. Lowering priority to P3.
Hi Jan, did you ever try to install J2SDK to fresh OS (lets talk about UNIXes, I'm not so familiar with WinXX) and then install from current NB installers IDE and the run the NetBeans ??? Did you succeed ??? Sorry I'm not :-( Where the problem ??? I know it ;-)) Problem is that 'runide.*' and other scripts depends on system variable JDK_HOME and this varable is NOT set during the J2SDK installation process !!! So that's why I fill this bug and set priority to P2 (final this is P2 so I changed from P3 to P2 again). Next comment: AFAIK the installers are for BIGINNERS with Java and NetBeans ... this is not my thaught but UI definition in "http://ui.netbeans.org/docs/hi/install_support/InstallersUIS.html" in section "User View | Description of the Users". Do you think that Java biginner will know what all have to be set as a postinstall ??? I think not ;-) And last think: I think you didn't read the history of the bug before you set priority to P3 ... please read carefuly my first comment form 2002-06-08 08:27 PDT.
Thank you for making it clear. Yes, I see a problem for beginner user to run an *installer*. Installer is java app that runs on same jdk as NetBeans. If the installer is running why should it ask beginner user for jdk? Beginner user doesn't won't to provide anything like java home in installer. She just wants to install and start IDE successfully. If installer can find jdk then shell script should find it too. If it can't then file a bug against it. I am closing the bug as wontfix as original request for choosing different jdk than installed is clearly enhancement. Please reopen as enhancement or file a new one.
Ji Jan. Big sorry to say:"You are not clear with it". I expect your working platfor is Windows and not UNIX/Linux :-( Once again. The Installer looking for JDK at predefined paths and *sh scripts looking for JDK set in JDK_HOME by befault. If the JDK_HOME wariable missing runide.sh script inform you about this and you: a) have to set this variable b) run script with -jdkhome switch I expect, that installer is for installing the product and not only enable you to choose destination directory and then say to you you have to do another posinstall step(s) :-( That's why I fill this bug and once again reopen it !!! Currect state of the installer is same as tar ball ... .
I forget to add another comment. Different paths (installer x runide.sh) are reason why I'm askung for new panel in installer, which will enable you choose propper JDK for executing *sh scripts.
I am linux user even though I don't understand why ide launcher can't search for jdk just as installer launcher does it. I am also saying that extra installer panel won't fix the real problem. If installer starts up without specifying jdk path then IDE should start too without asking for it.
Well, if you try to look into final installer file for e.g. Linux, the InstallShield build into this binary file section with hints for paths, where expect installer JDK. Somethink like: PATH_HINT: "/usr/jre1.4" "/usr/local/jre1.4" "/opt/jre1.4" /: PLATFORM_HINT: JAVA_HOME JDKHOME You can see the NetBeans *.sh scripts using a bifferent system variable, which specify JDK path: IS uses JAVA_HOME NB uses JDK_HOME Next what you can see is that there are hint in IS like "/opt/jre1.4" or "/usr/local/jre1.4" ... these are paths the IS looking for JDK at. You said: "I don't understand why ide launcher can't search for jdk just as installer launcher does it". Wuld you like to specify all possible JDK paths in the runide.sh script (and others) ??? Realy ??? The *.sh script is universal for different kind of UNIX systems ... a lot of paths ;-) Next think. There is installer and this installer have predefined JDK1.4.0, final installer. I install JDK1.4.0_01 ... during building of this installer the JDK1.4.0_01 was unknown. So you upgrade you JDK from 1.4.0 to 1.4.0_01 form e.g. RPM package ... rpm will create another directory with name j2sdk1.4.0_01. And now, installer know only JDK1.4.0 and I want to use JDK1.4.0_01 ??? How to do that with the installer ??? If you said the *.sh script have to use same JDK as installer ??? Finally: a new pane will fixt the problem. If you want to see it in the real world please call me.
Good news is that we control (means that we can change) paths and env variables where installer launcher and ide launcher searches for the jdk. So it is not a problem to synchronize them. Installer panel wouldn't solve the real problem of starting up the installer (I even didn't call you to know that). I am repeating myself that if installer starts up without asking for jdk then the IDE should start up too without doing it.
Set target milestone to TBD
Accoroding to discussion with Patrik I change priority of this bug to P3. There is fixed bug #25524 which improves installer work in this area.
This is an enhancement and depends on HIE review.
Don't think so :-( AFAIK the NB is designed to be used with more then one JDK, so why not enable to choose one ??? Strongly disagree with you. If you want to restrict the NB users, then bundle NB with JDK ... .
Just curious what you mean when you say than NetBeans is designed to be used with more then one JDK, can you give more details about what the usage scenarios are?
Hi Honza Formanek, there is answer: by "is designed to be used with more then one JDK" i ment that the NB can be used with more then one version of JDK (the JDK is NOT bundled with NB), right now you can use 1.3.1 || 1.4.0 || 1.4.1, so I expect I can choose one during the installation process. Probably the sentence is not so clear.
Implemented in 3.6. Marked as Fixed.
Verified