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.
040720, 1.5.0 b58, Ocean (= Metal on 1.5). It seems it is no longer possible to double-click lines in the Call Stack view to jump to the corresponding sources. This is annoying; have to use Fast Open and Goto instead. Tried both Name and Location columns. No hyperlinks displayed.
I cannot reproduce it. Clicking in the Name column seems to jump to the correct execution point. I tried 1.5.0-b58 on WXP and 1.5.0-b59 on Fedore Core 1. Both work well. Reopen if you are still able to reproduce it.
True, double-clicking does work. However there are two problems relative to 3.6: 1. There is no underlining or other visual marking on the Name column entries to make it clear that you can click them. For example, you cannot click the Location column, even though intuitively that might be what you would expect to be hyperlinked. Currently you see e.g. ClassPath.getRoots:163 ClassPath.java with only the first hyperlinked, which in all makes little sense IMHO; would expect ClassPath.getRoots ClassPath.java:163 or ClassPath.getRoots ClassPath.java:163 in /space/src/nb_all/java/api/src/org/netbeans/api/java/classpath/ with either both columns or only the second one hyperlinked. 2. There is no visual distinction between classes that you do have source for and those which you do not. This is what led me to believe that there was no hyperlinking at all: most of the classes in the stack trace were in JUnit (debugging a unit test) and I had no source; but these lines look the same as the one or two lines in my own code for which I have source, and clicking the JUnit lines silently does nothing. So trying a few lines at random I came to think that none of them worked.
*** This issue has been marked as a duplicate of 48174 ***
Sorry, it was mistake.
Hyperlink should be added there. Or at least "Go to source" context action.
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. We apologize for any inconvenience. Thank you. The NetBeans Team
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.