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 26440 - Ability to monitor class-usage per process
Summary: Ability to monitor class-usage per process
Status: NEW
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-10 22:10 UTC by _ gtzabari
Modified: 2007-01-04 20:50 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
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 2002-08-10 22:10:47 UTC 
Users should be able to monitor processes
invoked through Netbeans to see exactly which
classes are being used. The idea is to resolve
classes being used back to their filenames in the
file-system.

   Reasoning: people often waste days at a time
trying to resolve problems caused by having
different versions of the same JAR in their
classpath. Had they had the ability to see which
versions of the library is being used they would
have noticed their problem. This is kinda like
solving DLL problems for native processes.
Comment 1 _ rkubacki 2007-01-04 20:50:31 UTC 
Not a core responsibility. Somewhere between profiler (according to summary),
debugger and java projects.