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 84043 - Installation failure if default installation directory not used
Summary: Installation failure if default installation directory not used
Status: RESOLVED DUPLICATE of bug 64380
Alias: None
Product: ide
Classification: Unclassified
Component: BlueJ (show other bugs)
Version: 5.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: mslama
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-01 16:29 UTC by cpjobling
Modified: 2006-09-13 09:39 UTC (History)
1 user (show)

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 cpjobling 2006-09-01 16:29:38 UTC
This may be related to issue 84041. I tried to install Netbeans 5.0 BlueJ
edition but installer failed after JDK selection. I didn't accept the default
installation location (c:\Program Files\netbeans-5.0-bluej [or whatever])
instead I browsed to a location where I like to keep my Java applications on a
separate partition (I chose folder d:\java\apps\netbeans-5.0-bluej). Installer
appears to start but quits without any warmings. I have write access to the
installation location that I want and I have JDK 1.5.0_06 installed and
selected. I have not tried to install BlueJ edition using the defaults. Neither
do I have any problem installing BlueJ nor Netbeans.
Comment 1 Milos Kleint 2006-09-01 17:25:55 UTC
marek, please evaluate. This is installer related.
Comment 2 mslama 2006-09-05 14:27:44 UTC
When does installer quit? After you press Next on Preinstall summary panel ie.
just before install action starts? In such case it could be caused by Swing
problem with broken desktop theme (Swing retrieves unexpected value from desktop
theme). Workaround is to switch to default desktop theme. To verify this cause
please attach install.log file from <Selected install folder>\_uninst
Comment 3 mslama 2006-09-13 09:39:35 UTC
No feedback. I assume it is duplicate of issue #64380. Workaround is to switch
to default desktop theme or update to latest JDK 5.0 update where this problem
should be already fixed.

*** This issue has been marked as a duplicate of 64380 ***