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 85414 - Linux installer doesn't automatically find JDK 1.6.0
Summary: Linux installer doesn't automatically find JDK 1.6.0
Status: CLOSED FIXED
Alias: None
Product: installer
Classification: Unclassified
Component: NBI (show other bugs)
Version: 6.x
Hardware: PC All
: P3 blocker (vote)
Assignee: dlipin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-21 09:30 UTC by Marian Mirilovic
Modified: 2010-04-22 10:33 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Mirilovic 2006-09-21 09:30:47 UTC
NB 5.5 (200609210000)
Linux Ubuntu 5.0.6 / Gnome

I tried the last available installer for linux. The installer found JDK 1.5.0_09
but hasn't found JDK 1.6.0 (b99). Both JDK's folder are located under the same
parent folder.
Comment 1 Marian Mirilovic 2006-09-21 10:02:21 UTC
OK, here is my filesystem structure :

/local_export/jdks/jdk1.5.0_08  - found
/local_export/jdks/j2sdk1_5_0   - found
/local_export/jdks/jdk1.6.0-b99 - not found
Comment 2 Marian Mirilovic 2006-09-21 10:25:00 UTC
Marek, 
please add your comments here !

BTW: well I understnad that /local_export is not 'usual' place to look for JDK
as well as I understand that you are looking for JDK on some 'usual' places.
From my point of view, it would be probbably expected to look for JDK at the
parent folder of 'current' JDK, just because users are usually installing JDKs
under one folder.
Comment 3 mslama 2006-12-13 17:46:24 UTC
Do you mean JDK for IDE in JDKSelection panel? I assume it. Installer path hint
and also adds current JDK (ie. JDK used to run installer itself). And it might
be reason for that as installer launcher uses more hints (like some environment
variables or user can even tell installer JDK location using -is:javahome).
JDKSelection panel uses some compromise algorithm and it is NOT complete search.
It is compromise to be fast enough and find JDK at common places ie. to cover
most cases. It would be possible to add some locations to search but it must be
some commonly used location.

Looking at parent of current JDK seems good. Passing to new installer to
consider it.
Comment 4 dlipin 2006-12-15 08:30:27 UTC
Scheduled for implementation in the next milestone.
Comment 5 dlipin 2006-12-20 12:35:54 UTC
Seems to be fixed.
Now the installer also search at all childs of the parent of the current running 
JVM. If the installer runs on the private JRE (that is located at <JDK-
Location>/jre) then it searches in one-up level instead.
Comment 6 Marian Mirilovic 2010-04-22 10:33:12 UTC
v/c