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 in files does not handle multiple top level classes well | ||
---|---|---|---|
Product: | java | Reporter: | Petr Jiricka <pjiricka> |
Component: | Unsupported | Assignee: | issues@java <issues> |
Status: | CLOSED INVALID | ||
Severity: | normal | CC: | tpavek |
Priority: | P4 | ||
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Petr Jiricka
2000-08-11 19:07:08 UTC
After the .java file is compiled, the "ClassFileData.class" becomes a separate data object - it is not recognize as a part of ManglerImpl (this is a matter of java module I think). The class object has its own node in explorer now. The searching algorithm just scans data objects (all in general) - that is why it scans "ClassFileData.class" too. (You can set restrictions on types of objects you want to search anyway.) Should this report be re-assigned to java module? You could help to set option Parse class file (Project options|Java sources) to true and restart IDE then. Then in Explorer will not appear class file nodes from compiled other top-level classes and so they will not be used for search. Yes, it is indeed a sideefect of the option Petr Slegr mentioned being turned off. This is the default setting because it may slow down the whole IDE. Resolved for 3.3.x or earlier, no new info since then -> closing. Resolved for 3.4.x or earlier, no new info since then -> closing. |