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 61053 - Launcher doesn't detect JDK if netbeans.conf is erroneous
Summary: Launcher doesn't detect JDK if netbeans.conf is erroneous
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 4.x
Hardware: All All
: P4 blocker (vote)
Assignee: _ rkubacki
URL:
Keywords:
Depends on: 74497
Blocks:
  Show dependency tree
 
Reported: 2005-07-16 11:28 UTC by muzzz
Modified: 2008-12-23 14:33 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description muzzz 2005-07-16 11:28:42 UTC 
If the jdk_home property in netbeans.conf is not pointing to a valid JDK
installation, the application exits after stating something along the lines of
'cannot find java.exe'.

It could be expected to search for a suitable JDK on it's own in this scenario,
just as it does when the jdk_home property is completely missing.
Comment 1 Pavel Rehak 2005-07-18 13:18:58 UTC 
Sounds more like enhancment for me, can you look at it Core guys?
Comment 2 _ rkubacki 2006-04-14 18:36:45 UTC 
If someone *sets* netbeans_jdkhome than it should be used. It might be confusing
to actually use different JDK. 

We will rather focus on better selection of JDK before we fallback to this property.
Comment 3 muzzz 2006-04-15 00:40:10 UTC 
Reopening the issue since the reasoning behind WONTFIX does not satisfy.

The issue is not limited to setting a non-existent JDK, but also occurs when
e.g. the JDK referenced in netbeans.conf is deleted. In this case I can not see
any confusion when falling back to the system default JDK, or whatever NB does
when jdk_home is not set.
Comment 4 _ rkubacki 2006-04-18 09:33:23 UTC 
Now I see - installer sets the jdk during installation.
Comment 5 mslama 2006-04-18 09:55:30 UTC 
Installer allows user to select JDK to run IDE and uses selected JDK to run
storage builder (preparses JDK sources). Then installer passes selected JDK to
IDE in netbeans.conf. If this way should be cancelled installer must use THE
SAME way as IDE to select default JDK when IDE is started for the first time (of
course this can work only when installed JDKs are not changed between
installation and first IDE usage).

Conclusion: To fix this issue installer must know how to select default JDK and
if/how to inform user about selected default JDK.
Comment 6 steevcoco 2006-05-26 23:09:38 UTC 
Hi.

I'll second the validity of this issue, since I was about to file an issue after
installing -- or more specifically, upgrading -- my JDK to the 1.5_07 release,
at which point NetBeans refused to launch.  I had to re-download the NB
installer and re-install it to get it to use the new JDK.

Thanks.
Steven Coco.
Comment 7 _ rkubacki 2006-07-11 16:35:09 UTC 
seems to be fixed now
Comment 8 _ rkubacki 2006-07-11 16:36:05 UTC 
done together with issue #74497
Comment 9 Quality Engineering 2008-12-23 14:33:34 UTC 
This issue had *1 votes* before move to platform component