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.
041022 custom, 1.5.0. I noticed that if you have a project (j2seproject, or freeform w/ "debug.fix" action binding) that is *not* set as the main project, and you debug it (e.g. by right-clicking the project node), then select a class in the app, Debug -> Fix will still be disabled. However if you set the project as the main project, Debug -> Fix will become enabled (and work fine). This looks like a bug to me. What difference does it make whether this is the main project or not? If the files belong to a project with a 'debug.fix' binding, you can call it, just like F9 is available regardless of the main project (etc.). Would be P3 - an odd thing - if that were all there was; but I also found that if you have j2seproject A depends on j2seproject B, and set A as the main project and debug it, you can invoke Fix on classes in A but not on classes in B. This effectively means that Fix & Continue is not available for subprojects (unless you know the unintuitive workaround: temporarily set the main project to the project with the files you want to reload). I think I mentioned this before as an aside in various other bug reports, but never reported it alone (IIRC).
Looks like we are using main project for fix&continue action in place of the project the current file belongs to.
Right. I guess the confusion is because F&C is the only debugger-related project action which is sensitive to the particular file selection.
Fix action now acts on the current file's project instead on the main project. /cvs/debuggerjpda/ant/src/org/netbeans/modules/debugger/projects/FixAc tionProvider.java,v <-- FixActionProvider.java new revision: 1.14; previous revision: 1.13
Verified in nbdev 2005070601800.