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.
Summary: | Project Groups confuse the breakpoints list | ||
---|---|---|---|
Product: | debugger | Reporter: | swpalmer <swpalmer> |
Component: | Java | Assignee: | Martin Entlicher <mentlicher> |
Status: | CLOSED FIXED | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
swpalmer
2007-12-13 17:05:16 UTC
Reassigning to "debugger" for evaluation. Well, the breakpoints are always set on the original file where was it created and is it bound to the particular project. Project groups are logical sets of projects only, we do not propagate all breakpoints from projects into projects with the same name in other groups. I do not think that this is really desired, since you can have different line numbers and different code in different projects. I don't expect the breakpoints to be propagated. I expect the set of breakpoints to be either cleared or saved/restored with the project group change so that when I switch groups the breakpoints list doesn't show irrelevant and confusing things. As it is, the UI is left in a state that leads to problems - there isn't an easy way to see that the breakpoints list is not referring to a different project (since my projects are all the same names and files, the groups are based on the trunk vs. a maintenance branch of the code). This in turn can lead to accidental edits on the wrong file. Changing TM for open issues. The breakpoints window will hopefully be improved into NB 7.0. This should be fixed by implemented enhancement #101195 - by default we show only breakpoints from the opened projects. Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier. |