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.
[release40 RC1] Action Step Into works only for Main Project. From the name of the action it's not obvious that it should work only for Main Project. What if user wants to Step Into non Main Project, does he need to set it as Main Project just because of debugger start? Also it would be very useful to be able start another session by Step Into invoked on another (non Main) project.
As designed. See http://debuggercore.netbeans.org/UI/UsersView-40Features.html
BTW. If you have some idea how to improve our current design, feel free to write some UI spes and fire a RFE for it. Saying that some action should do something different is not enough. We need complete design...
I'm not a designer, but quality engineer. That means that I do care about quality and usability of the product. The spec mentioned by you is not product of any UI research or usability study, it's just the way how you saw it when you wrote it. Current design of Step into action is not optinal IMO. That's why I filed this issue. I apended kw USABILITY, that means that issues might affect user workflow. I expect somebody from HIE to express opinion too. BTW, correct resolution of such issue would be INVALID or WONTFIX but not WORKSFORME. Proposed behavior of Step into action: 1) If no project node is active then Step into Main project 2) If some project node is selected in Explorer then Step into the selected project, that would apply also when another session is already running.
Definitely not a bug. Written according a spec. BUG=>ENHANCEMENT
The same applies for Run to cursor action. It unexpectedly starts to debug the main project, not the current source. The design of these actions needs to be reevaluated...
From my point of view the Step Into and Run to Cursor should start main project in debugger, only if the current source file is on classpath of the main project. If it's not, it should ask what to do: Run in Debugger: (o) "<this project>" Project ( ) "<this file"> File ( ) Test File Or something like this: Run in Debugger: (o) Project: |_<this project>______v_| - this is a combo containing all projects ( ) File "<this file name>" ( ) Test File "<name of test of this file>" Note, this is not a spec, just an idea :-).
Needs to be reevaluated in light of bug #166780.
Bug #166780 did not change anything but the default state. Therefore it does not mean anything for this issue. There is still a set of projects, or one main project and others. The current behavior is similar to the proposed one by Jano: Step Into and Run to Cursor start main project in debugger, only if the current source file is on classpath of the main project. If it's not (including the case when there's no main project set), they start the selected project. The problem arise, when the user want to debug an individual file or test file. "Debug File" or "Debug Test File" has to be used for that purpose. Since Step Into and Run to Cursor works as expected IMHO, resolving as fixed. For the case of stepping into a particular file or test file, we have bug #148377.
(In reply to comment #8) > Bug #166780 did not change anything but the default state. Therefore it does > not mean anything for this issue. It affects the priority. > Since Step Into and Run to Cursor works as expected IMHO, resolving as fixed. Rather WORKSFORME, since you did not make any changes to resolve this bug.