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 47565 - [40cat] No installation with JDK1.4.2 on WinXP possible
Summary: [40cat] No installation with JDK1.4.2 on WinXP possible
Alias: None
Product: installer
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: mslama
Keywords: RELNOTE
: 47564 (view as bug list)
Depends on:
Reported: 2004-08-20 15:51 UTC by voigtje
Modified: 2004-08-23 14:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

log file of failed installation (9.27 KB, text/plain)
2004-08-23 13:36 UTC, voigtje

Note You need to log in before you can comment on or make changes to this bug.
Description voigtje 2004-08-20 15:53:59 UTC
[ JDK VERSION : J2SE 1.4.2_05 ]

I tried to install beta 1 on WinXP with only JDK1.4.2 installed.

The installation did not start, but complained about a missing JDK. The same result when I startet the installation from the command line (cygwin-bash) with the option -is:javahome <home of my JDK1.4.2>

Then I installed JDK 1.5.0beta2.

With that JDK NB4.0beta1 could be installed without problem.

Thus, NB4beta1 refuses to install with JDK1.4.2. 

Is this intented or a bug??
Comment 1 mslama 2004-08-20 17:21:53 UTC
Native installer launcher looks for installed JDK in registry and by
path hints. If you installed JDK 1.4.2 by installer it should be found
by installer. Please run installer from console with -is:log
<logfilename> eg. -is:log installer.log and attach created log. (This
log is from native launcher with info about JDK search. Launcher
searches JDK 1.4.2 (1.4.2_X) first then JDK 1.5.0.
Comment 2 mslama 2004-08-23 09:48:42 UTC
*** Issue 47564 has been marked as a duplicate of this issue. ***
Comment 3 voigtje 2004-08-23 13:01:51 UTC
I could install NB4.0beta1 with the following command line:
-is:javahome $(cygpath -w /cygdrive/c/jdk1.4.2)

So obviously the problem was my cypath. 

Also, other users reported no problems on WinXP with JDK 1.4.2 on 40cat.

Mark as resolved (worksforme) ??
Comment 4 mslama 2004-08-23 13:19:56 UTC
As I said log from native launcher would tell us why your JDK was not
found. If you would use JDK installer it creates item in registry
which should be detected by native launcher of NB installer regardless
of its location. If you want to find out more run installer with
-is:log <logfilename> option and attach it here.
Comment 5 voigtje 2004-08-23 13:36:23 UTC
Created attachment 17028 [details]
log file of failed installation
Comment 6 voigtje 2004-08-23 13:45:38 UTC
I submitted a log file of a failed installation as requested.

Obviously, the log file tells us that the NB installer looks only for
JDKs in the directories with unchanged original names from the Java
installer, e.g. c:\j2sdk1.4.2.

On my computer, I renamend my Java directory into c:\jdk1.4.2. This
renaming obviously caused the problem.

I don't think one can prohibit users to rename their Java dierctories.
The JDK installation allows renaming and placement of the JDK in any
artificial places.

Marek, do you agree? Should we reopen the issue?


The error message ("No JDK found") also tells the user where a JDK was
looked for or advices to produce the log file as you did now. 
It is quite strange to have running JDK(s) properly installed, but
having NB installtion telling me it could not found a JDK.
Comment 7 mslama 2004-08-23 13:55:15 UTC
JDK installer stores JD location in registry. So you can install JDK
anywhere and it should work. But if you rename installation dir AFTER
installation search will fail. On Linux I get following message if JDK
cannot be found: A suitable JVM could not be found. Please run the
program again using the option -is:javahome <JAVA HOME DIR>. I think
it is enough. What error message did you get on Windows when JD was
not found?
Comment 8 _ ttran 2004-08-23 13:59:27 UTC
If the user renames the install dir he risks more things stop working,
for example the java plugin.  The installer cannot do an exhaustive
disk search.

But I think we should document the -is:javahome <pathtojdk> switch on
a prominent place on the web, perhaps on the same page as the
download.  Otherwise more people will run into trouble without knowing
how to fix
Comment 9 voigtje 2004-08-23 14:05:33 UTC
Under WinXP I got the same message as you.

I checked my registry: You are right, it contains the wrong place for
my JDK. So obviously I renamed AFTER installation. Usually I do
within, hmmm.

I always work with cygwin where I have my own paths set. That is why I
didn't realized the wrong registry entry before.

Summary: My fault. 

Thx for the help.