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.
There is a "pseudoofficial" debugger API which is more or less project private contract between debugger and other modules. But because a lot of modules need to access debugging features, there seems to be a need for real and commited interfaces that will follow the rules and standards common to NetBeans APIs. Let's create new module (or more modules) that will put API into org.netbeans.api.* and org.netbeans.spi.* packages.
homepage for Debugger API: http://debuggercore.netbeans.org/docs/api/index.html Target milestone: Promo D (see Integration plan for more info) all info required for Architecture Review Step 1 are linked on Debugger API homepage
This definetely needs standard review. I think we have all the documents needed for inception review so let's get started reviewing (step 6 in:) http://openide.netbeans.org/tutorial/review-steps.html Please comment. I am setting the target date for Tue 11/25.
Planned for Promo D
Let's do another review of the current state, before it appears in main trunk. I think Mar17 could be nice date. Hanzi, please prepare materials for review week before then.
Architecture Questions document is updated in trunk. All other documents and JavaDoc are linked form: http://debuggercore.netbeans.org/docs/api/index.html
Hanz requested change of the review date to 03-23-2004, I agreed and I hope that it is ok for Tomas.
My expectation is that after redesign new debugger should fix breakpoint deserialization. It should not be done eagerly during startup but lazily on demand when debug session is started/ file containging breakpoint(s) is edited. Is this solved?
This is not Debugger API related problem as I know. Ant it is not addressed yet. We can listen on files opened in editor and add annotations on them lazily. Can you create a separate issue for this perofrmance problem?
Maybe it is not related to your API. You can treat #41192 as a separate issue in such case. Anyway I am surprised that it was not included into refactoring plan.
Review is done, the opinion document can be found at: http://openide.netbeans.org/tutorial/reviews/opinions_27194.html
fixed in the main trunk
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.