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.

Bug 123970 - Project Groups confuse the breakpoints list
Summary: Project Groups confuse the breakpoints list
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-13 17:05 UTC by swpalmer
Modified: 2010-04-29 09:37 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description swpalmer 2007-12-13 17:05:16 UTC
I create different project groups for different versions of the same project (e.g. maintenance branch and trunk).  When
switching between project groups the breakpoints list seems to refer to files in the group they were created in - NOT
the current project group.

This means that double clicking on an item in the Breakpoints list will load a file from the wrong project and it will
be easy to accidentally change that file.

E.g. Assume two Project Groups  "Maintenance" and "Trunk". They have identical projects that come from two different
directories on the disk.  E.g. C:\dev\maintenance\Project1  and  C:\dev\trunk\Project1

If a break point is set in Main.java while working on the "Maintenance" project group then we switch to the "Trunk"
product group the breakpoint list is not changed.  While working in the Trunk group a double click on the breakpoint in
the breakpoint window will load C:\dev\maintenance\Project1\src\Main.java NOT C:\dev\trunk\Project1\src\Main.java which
can easily go unnoticed.
Comment 1 Peter Pis 2008-01-04 09:38:22 UTC
Reassigning to "debugger" for evaluation.
Comment 2 Martin Entlicher 2008-01-07 13:37:02 UTC
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.
Comment 3 swpalmer 2008-01-08 14:11:49 UTC
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.
Comment 4 Peter Pis 2008-04-10 22:54:22 UTC
Changing TM for open issues.
Comment 5 Martin Entlicher 2008-11-10 15:42:11 UTC
The breakpoints window will hopefully be improved into NB 7.0.
Comment 6 Martin Entlicher 2010-02-08 03:36:13 UTC
This should be fixed by implemented enhancement #101195 - by default we show only breakpoints from the opened projects.
Comment 7 Quality Engineering 2010-04-29 09:37:29 UTC
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.