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.

Bug 163569 - Add an option in installer to disable setting particual JDK for NetBeans usage
Summary: Add an option in installer to disable setting particual JDK for NetBeans usage
Status: NEW
Alias: None
Product: installer
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker with 1 vote (vote)
Assignee: Libor Fischmeistr
URL: http://www.netbeans.org/servlets/Brow...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-24 11:16 UTC by dlipin
Modified: 2014-02-10 14:15 UTC (History)
4 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dlipin 2009-04-24 11:16:01 UTC
Sent by Brett Ryan (brett dot ryan at gmail dot com) to netcat alias.

The other thing is, why does a default install explicitly set the netbeans_jdkhome in the conf file? Commenting this on 
windows correctly starts the IDE with my default JDK, I haven't tested this with windows as I'm not at home. If I 
remember correctly 5.5 and prior came shipped with this commented. Upgrading/removing your old JDK always breaks this 
and you have to change it in the conf file anyway.
Comment 1 dlipin 2009-04-24 11:18:16 UTC
Tonda says:

Some users frequently update their JDK/JRE installation and when they remove the old JDK NetBeans cannot start anymore 
due to the hardcoded path in netbeans_jdkhome property.

On the other hand, for some other users (perhaps majority?) setting netbeans_jdkhome by the installer works OK and it 
allows them to pick a certain version of JDK from several versions already installed.

How about allowing the user to click a new checkbox in the installer, which would mean "do not set specific JDK and let 
launcher pick a JDK"?

At least on Windows, this could work well.
Comment 2 dlipin 2009-04-24 13:32:27 UTC
Ondrej, could you please suggest the UI for that?
Current UI is close to 
http://ui.netbeans.org/docs/hi/nbi/images/nbi-wizard-ide-select-jdk.png

Thanks.
Comment 3 dlipin 2009-04-24 13:35:55 UTC
I personally can image 3 solutions:
1) Single check box "Use default JDK for NetBeans"
2) 2 radiobuttons, one enables JDK combobox and another disables it with displaying message about default JDK been used
3) Add "Use default Java/JDK" in the JDK combobox - but it won`t be visible if we don`t make it the default choice 
(presonally I don`t think it is a good idea)
Comment 4 Ondrej Langr 2009-04-28 20:12:59 UTC
I'm not sure I understand the problem clearly. Let me paraphrase to make sure I understand.

The problem is, that if a JDK is moved/removed, IDE can not start, right? 

The suggested solution is to add an option for using default JDK, but if that option is not selected at install time
(users can choose to run particular JDK yet remove/move it later, right?) users can run into this problem anyway, right?

If I got all the above OK, the ideal solution from users' point of view seems to be to have "use system-default
Java/SDK" option as a default in the combo-box (point 3 in Dmitry's post). However, now the fact that we prefer users to
use certain versions of JDK over anothers comes into play and makes it more complicated, right?
Comment 5 dlipin 2009-05-12 17:16:12 UTC
> The problem is, that if a JDK is moved/removed, IDE can not start, right? 
Right.

> The suggested solution is to add an option for using default JDK, but if that option is not selected at install time
(users can choose to run particular JDK yet remove/move it later, right?) users can run into this problem anyway, right?
Right.

> If I got all the above OK, the ideal solution from users' point of view seems to be to have "use system-default
Java/SDK" option as a default in the combo-box (point 3 in Dmitry's post). 
> However, now the fact that we prefer users to use certain versions of JDK over anothers comes into play and makes it 
more complicated, right?
Alsmost, right, again:) We don`t want to users to use "certain" versions of JDK but rather use the "latest stable 
update" of JDK (at least, in installer) that is available on the system.
Comment 6 Antonin Nebuzelsky 2009-05-12 21:56:46 UTC
It is too late for such experiments in 6.7 now.

For the next release, it would be good to have a change in daily builds very soon, and watch closely user feedback.
CCing also QA.

BTW, Ondrej's comment about this option turned on by default make sense.

BUT we cannot make sure that the latest version on user's system is the default one. User might have installed some old
version intentionally as the last one, maybe to test something, and this one might be marked as default in Windows
Registry. Is it correct, Tomas?

Any suggestions how to make this work correctly, taking always the latest stable JDK installed?
Comment 7 t_h 2009-05-13 07:10:02 UTC
> User might have installed some old version intentionally as the last one, maybe to test something, and this one might
be marked as default in Windows Registry. Is it correct, Tomas?

No, I think the default is the latest version not last one installed. So if no version is specified the latest is used.
If invalid (non-existing) version is specified, dialog shows asking whether default version should be used instead.
Comment 8 Jiri Rechtacek 2012-10-07 12:58:59 UTC
Assigned to new owner.