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: | Users don't understand "Apply Code Changes" label | ||
---|---|---|---|
Product: | debugger | Reporter: | _ tboudreau <tboudreau> |
Component: | Code | Assignee: | issues@debugger <issues> |
Status: | CLOSED WONTFIX | ||
Severity: | blocker | CC: | arseniy, pjiricka |
Priority: | P4 | Keywords: | SIMPLEFIX, USABILITY |
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
_ tboudreau
2006-08-12 15:40:48 UTC
FYI: Xcode has "Fix and Continue", IDEA has a "Reload Changed Classes" dialog. It looks like there is no common term for this... Long-term, after we have instant compilation, we might get rid of this and upload the changed classes automatically... FYI: see issue #40440. "Compile & Fix" looks good to me... The root cause of this problem is IMHO not the name of the action but the necessity to use it. For next NB release we will try to eliminate it doing 'Apply Changes' automatically after 'save' -- like Eclipse does. For NB 6, keeping this issue opened, P3->P4, since there is really not any standard name and many NB users are familiar with 'Apply Changes'. This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. We apologize for any inconvenience. Thank you. The NetBeans Team v/c |