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.
This relates to the use of Sierra and was found in MS4. After installing Sierra with a JDK that the user then wishes to switch out, they need to resort to config files / batch files to do so for the IDE and app server. There needs to be an installer modification program to assist changing the desired JDK version for Sierra use. During the CEW4 workshop, we needed to switch to JDK 1.5 (from 1.6) since the Oracle OTD had some dependencies on 1.5. To do so we needed to: 1.Change netbeans_jdkhome to use JDK 1.5.0 in C:\JavaCAPS52\netbeans\etc\netbeans.conf 2.Change “set AS_JAVA=C:\...\jdk1.x\jre/..” to use JDK 1.5.0 in C:\JavaCAPS52\glassfish\config\asenv.bat
lpolycarpou, to my best knowledge, neither the NetBeans installer nor the underlying NBI engine are used for JCAPS Sierra installation. Thus, obviously this bug does not really belong here. I'm unsure, what is the proper location, however.
I don't think this issue is specific to Sierra or installation for that matter. Customers just need an easier way of changing the JDK version for NetBeans and Glassfish from the IDE itself post-install. At the moment, they have the option to do this using startup parameters / config files. For instance: * It would be useful if the NB6 environment itself had a dedicated Option, in the Tools | Options dialog, for switching the JDK version. After all, you can change the Ant version in this way, so why not the JDK? * We should also add something in the Glassfish properties to determine which JDK version NB6 uses for starting Glassfish.
> * It would be useful if the NB6 environment itself had a dedicated Option, in the Tools | Options dialog, for switching the JDK version. After all, you can change the Ant version in this way, so why not the JDK? simply because you are running on the JDK, so you can't change it for running IDE -> WONTFIX for Glassfish issue reassign to serverplugins
A bit of odd logic here IMHO.. > simply because you are running on the JDK, so you can't change it for running IDE -> WONTFIX What about change the settings + require IDE restart for them to become effective? Happens every now and then in modern software. Even if I install a small plugin I'm required to restart the IDE quite often..
I would like to resolve this in the GF v3 plugin. the v2 plugin is not going to get this enhancement.
users can change the java executable that is used to run the v3 server