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: | *Find Usages* fails if refresh button is used | ||
---|---|---|---|
Product: | editor | Reporter: | dnikitin <dnikitin> |
Component: | Refactoring | Assignee: | issues@java <issues> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | issues |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
dnikitin
2008-04-01 16:27:49 UTC
I've made some investigations. This is the core refactoring problem, it's not C++ related (try in Java => same result). The problem is in AbstractRefactoring implementation. If cancel was set up once to true => then next Refresh always give 0 results, because of if (cancel) check in each method before asking plug-ins. I think "cancel" must be set to "false" when refresh is called. Easy workaround. Invoke Find Usages again. Not P2. Resolving all issues with milestone "future" as LATER. If you feel strongly that it should be implemented please reopen and set the target milestone to "next". NetBeans.org Migration: changing resolution from LATER to WONTFIX On elif some test is marked as "Known Failure" |