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: | There has to be Reindex/Refresh action for source node | ||
---|---|---|---|
Product: | php | Reporter: | Petr Pisl <ppisl> |
Component: | Code | Assignee: | Tomas Mysik <tmysik> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | jrojcek, pjiricka, rmatous, tmysik, tzezula |
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Petr Pisl
2008-10-20 09:12:33 UTC
This issue blocks usage of netbeans together with other external tools (details in previous comment)! Jano, any idea how to fix it from ui point of view? Adding refreshing action? Any objections? This is a problem not only for PHP, but also for Java - see issue 159631. Reassigning to Ondra L, I heard Jano does not have much time for NetBeans these days. Refresh action on respective nodes is probably the right way to go. I guess it should only be present on the nodes (Source Packages, Test Packages), not project on project node. Because what is essentially refreshed (or re-indexed) is really just project sources, not project configuration files. I would find it much better to have this action just on project node. Implementation naturally won't care about project configuration files. I don't think that users should care about what to refresh (sources, tests, selenium), after running any black box 3-rd party application or command. I will be the owner of this issue. I agree with Radek, "Refresh" should be on project's node (just one action, there can be more directories underneath project directory, not only sources or tests). No problem with me, sounds reasonable. Vita mentioned that the API is already there: it should be no problem adding the action to e.g. the PHP project node. I guess we can close this issue, we have Source > Scan for external changes action for NB 6.8. |