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 62703 - Can't install under Netbeans 4.2 dev builds
Summary: Can't install under Netbeans 4.2 dev builds
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-19 21:04 UTC by _ gtzabari
Modified: 2007-02-20 18:08 UTC (History)
0 users

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 _ gtzabari 2005-08-19 21:04:56 UTC 
The installer complains "You must specify the installation directory of Netbeans
IDE 4.1" when I explicitly point it to Netbeans 4.2.
Comment 1 Jiri Sedlacek 2005-08-22 06:00:41 UTC 
Current versions of Profiler are only for NetBeans 4.1 (see 
http://profiler.netbeans.org for more information), thus the installer doesn't 
allow to install it on other NB versions.
Comment 2 _ gtzabari 2005-08-22 06:04:25 UTC 
I understand, but what's the reasoning? I installed the profiler under Netbeans
4.1 and transplated it into Netbeans 4.2 and it started up just fine so as far
as I can see there is no technical reason to prevent people from installing it
under 4.2 dev builds. This used to work fine in older releases.
Comment 3 Jiri Sedlacek 2005-08-22 06:10:09 UTC 
For example, the Profiler relies on concrete versions of Tomcat or SJSAS 8.1PE 
plugin versions for J2EE profiling and currently can't work with another 
versions.

Will do more research if at least a basic subset of features could be available 
for 4.2.
Comment 4 iformanek 2005-09-12 16:09:53 UTC 
Fixed.
Comment 5 ehucka 2006-10-09 12:11:16 UTC 
Verification of old issues.
Comment 6 Alexander Kouznetsov 2007-02-20 10:13:08 UTC 
Closing old issues
Comment 7 Alexander Kouznetsov 2007-02-20 18:08:10 UTC 
Reverting to original Target Milestone value changed by mistake. Sorry for
inconvenience.