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 160496 - Call Hierarchy sometimes shows nothing
Summary: Call Hierarchy sometimes shows nothing
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Rastislav Komara
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-17 19:20 UTC by swpalmer
Modified: 2011-05-30 16:11 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 swpalmer 2009-03-17 19:20:52 UTC
The show Call Hierarchy feature sometimes shows a method as having to callers when it is quite obvious that it does.\NB 
6.5.1
Comment 1 dudy 2009-03-18 08:52:15 UTC
I also experienced this. I was not yet able to reproduce this.

There are more functions that won't work "sometimes". As mentioned, the call hierarchy while debugging is not visible. I also 
can't add a new watch. When I'm in the editor and want to "select in projects", the focus moves to the projects window but not 
to the requested file. And, the most curious for me, the "close project" menu item in the context menu of the projects window 
disappeared.

I'm with NB 6.5.1, JDK 1.6.0_12, OpenSuse 11.1 64bit, working on a JEE project with Server and AppClient parts.
Comment 2 Jiri Prox 2009-03-18 12:28:45 UTC
Does normal find usages works when Call Hierarchy fails?

dudy: please report the problems separately, they have to be evaluated by different teems. Thanks
Comment 3 David Strupl 2009-03-31 15:55:03 UTC
Resolving all issues with milestone "future" as LATER. If you feel strongly that
it should be implemented please reopen and set the target milestone to "next".
Comment 4 Quality Engineering 2009-11-02 11:16:13 UTC
NetBeans.org Migration: changing resolution from LATER to WONTFIX
Comment 5 swpalmer 2011-05-30 16:11:14 UTC
This is still happening with NB 7 patch 1... why is it being marked as WONTFIX?