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.
Created attachment 138822 [details] test case in zip file When debugging a Maven project, one sometimes wants to step into library code. This does not work if the source code is missing from the local repository. One can then navigate to the class file and click a button in the editor to attach / download the source. But this does not help during the current session. If I set a breakpoint on the new source code, then the debugger becomes aware of it, and it seems to act. But instead of stopping in the editor on the breakpoint, it shows the debugger console. My workaround is to re-open the project. To reproduce with the supplied web project: The web page has 4 links, click the last "PageWithLink" after setting breakpoints and connecting the debugger. set a breakpoint at: org.apache.wicket.Component.urlFor(Component.java:3382) public final CharSequence urlFor(final RequestListenerInterface listener, final PageParameters parameters) step down to return getRequestCycle().urlFor(handler); you hit org.apache.wicket.request.cycle.RequestCycle.mapUrlFor(RequestCycle.java:429) public Url mapUrlFor(IRequestHandler handler) { final Url url = requestMapper.mapHandler(handler);// Can't step into this.
We need to add listening on changes of projects sources. Currently, debugger gets a set of sources on it's start and there's currently no direct association of the sources with corresponding projects. Scheduling for the next release.