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.
[ BUILD # : M3 ] [ JDK VERSION : 1.6.* ] The "Go to implementation" navigation plugin has stopped working between M2 and M3. In previous versions (even 6.7M2) I was able to jump to an implementation of a method on an interface by placing the cursor on the method name and invoking the "Go to implementation" function from the Navigation menu. When I do that now a message appears on the status bar saying "No overriding method found".
Can you please attach messages.log? Where is the target of this jump? (in source of current project, in another project, in library or in JDK)
The target is a Class residing in the same directory as the interfaces. The project is a Maven EAR project and the interface is a local EJB interfaces and the implementation is a stateless session bean. "Go to implementation" works for the same code in 6.5 and 6.7M2.
Created attachment 79601 [details] NetBeans log
I will take a look.
In my experience, sometimes it works, sometimes it doesn't. Find Usages > Overriding Methods works more consistently.
@jglick, It worked perfectly in 6.5 and 6.7M2. The "find usage -> overridden methods" is not a proper alternative, as the "Go To Implementation" can be activated directly on the code after which the possible implementations pop up below the code. The "Go to implementation" method takes about 2 secs to complete where "find usage" takes 10-20 secs to complete depending on the speed of the programmer.
I did a minimal fix here: http://hg.netbeans.org/main/contrib/rev/9c5ffeeb4061 New version of the module is available on the Development Update Center (version 1.5). A reproducible test case when the action fails would be very welcome.
I just updated it today and tried it again and just got a dialog box saying "Cycle in dependencies".
Created attachment 79851 [details] Stack trace
Reproducible for me by selecting GtI on org.netbeans.modules.project.uiapi.ProjectChooserFactory.createSimpleTargetChooser with just projectui module open.
I can confirm that this has been fixed in 200904150201
Part of std. distro for some time now.