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.
Product Version: NetBeans IDE Dev (Build 200710250352) Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b02 1) Open/Create 1st visual web project 2) Toggle breakpoint in Page1.jsp 3) Open/Create 2nd web project 4) Togle breakpoint in index.jsp 5) 2nd Debug project 6) Close 1st project Now breakpoint in Page1.jsp is still listed. 7) Right-click on breakpoint -> Go to source Nothing has happen, as project is closed AND normal web project doesn't have Page1.jsp, so it can't be wrongly opened instead of original file from closed project (as it otherwise happens). This list should show only breakpoints in opened project.
Martin, "Breakpoint list lists breakpoints in already closed projects" - is this by design or is it defect just in web debugger? Thanks, David
This is probably by design, Breakpoints window shows just all breakpoints which are set, regardless of currently opened projects. The breakpoints are global, associated with IDE's user dir, not with the project. This is something we might change in the future, IMHO the breakpoints should be associated with the project. We already have an issue for that, I'll try to find it...
I've found several related enhancements. Issue #42266, issue #72560 and issue #101195. You may resolve this as a duplicate of some of these.
Thanks Martin, I thought so. As you are surely aware there is lot of subtleties which complicates it when it comes to storing breakpoints in project rather than in userdir. Eg. having open project A which uses closed project B you still want to step through the source code of project B and setting a breakpoint in project B would be stored in project A or (*closed*) project B? If you store it in project A then what happens if there is project C which is also using project B and you start debugging it? Perhaps concept of *main* project could be used but then if project A is main and you start debugging project C what should happen. Trickyyyy. *** This issue has been marked as a duplicate of 72560 ***