Bug 174774 - [68cat] Move debugger settings to project.properties
[68cat] Move debugger settings to project.properties
Status: NEW
Product: debugger
Classification: Unclassified
Component: Code
6.x
PC Windows XP
: P3 (vote)
: 6.x
Assigned To: issues@debugger
issues@debugger
:
Depends on: 166801
Blocks:
  Show dependency treegraph
 
Reported: 2009-10-16 18:47 UTC by ulfzibis
Modified: 2010-01-25 10:06 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ulfzibis 2009-10-16 18:47:52 UTC
[ BUILD # : 200910151401 ]
[ JDK VERSION : 1.6.* ]

If sharing a project, order of debug sources is an essential part of
a project. So those settings should be located in project.properties.
If sharing the debugger properties by help of export/import tool,
setting of all projects in the IDE will be saved in 1 file, so on
import in another IDE valid settings likely will be overwritten
erroneously.
Additionally saving the watches and breakpoints better go into
private.properties.
Comment 1 ulfzibis 2009-10-16 19:18:11 UTC
Another problem while saving in NB-user-dir is, those settings can't be versioned, and are not shareable between
developers via repository.
Comment 2 Martin Entlicher 2010-01-25 10:06:58 UTC
After issue #42266 was implemented, it becomes natural to start thinking about implementation of this requirement.

All watches and breakpoints are currently stored into a file under NetBeans' user directory. Those breakpoints that belong exclusively into some project (all line breakpoints, some field, method or class breakpoints) could be saved to and read from project properties. The rest (breakpoints in platform sources and other types like exception breakpoints, thread breakpoints, etc.) would still be saved into the file under NetBeans' user directory.
Possibly, we could introduce a possibility to bind a breakpoint to some project by user (e.g. I want a breakpoint in java.lang.String only when debugging project A).

Watches are not categorized at all. They are global and do not belong to any language or project. Some mechanism for watches categorization would have to be introduced in order to be able to store them into the relevant project.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo