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 194880 - NodeFinder should select *.class under Libraries
Summary: NodeFinder should select *.class under Libraries
Status: REOPENED
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 normal (vote)
Assignee: Martin Kozeny
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-30 17:41 UTC by opticyclic
Modified: 2013-02-14 13:17 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 opticyclic 2011-01-30 17:41:30 UTC 
Ctrl-Click on TopComponent
This goes to TopComponent class as you would expect.
However, the Projects view does not synchronise.
If you right-click on the tab of the TopComponent file you can click "Select in Projects"
However, this does nothing.

The jar that TopComponent is in should expand in the project view so that you can see where the class is
Comment 1 Jesse Glick 2011-01-31 15:33:09 UTC 
Right, Select in Project is designed for source files only. The NodeFinder for the logical view could jump to *.class files under Libraries, but I don't think this would be terribly helpful. More likely you wanted to jump to TopComponent.java in its source project, which will work if you open TopComponent.java located in a source project.
Comment 2 opticyclic 2011-02-01 22:10:20 UTC 
This is how it works in Intellij IDEA and it IS helpful.
In this particular example I wanted to see which jar the TopComponent was in.

In another case I wanted to browse the classes in the same package to look for possible implementations of a class.
Comment 3 Jesse Glick 2011-02-01 22:13:39 UTC 
Again - it would be better than nothing, but much better in most cases would be to ensure that you have source associations set up for the modules in your classpath (e.g. .../org-openide-windows.jar -> .../openide.windows/src/), in which case the owning project opens and you can see the class under Source Packages. Otherwise you can only look at class structure, not actual code.