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.
Currently, the files in which the IDE searches, are specified in the Find in Files dialog in the 'Object Name' and 'Type' tabs. This is not a good solution for several reasons. First, not all object types are intuitive and correspond to user expectations. For example, the 'HTML objects (executable)' or 'JSP-based Java Servlet objects' are not intuitive. Furthermore, with the changes in the OpenAPIs/Projects, it is not even necessary to provide a DataLoader (object type in the user terms) in order to give it functionality. So, the object type is not a concept that should be exposed to the user - it is only an implementation detail. [This is one of the places where the architecture "shows through".] Moreover, the dialog does not easily allow searching in e.g. all *.dat files. Next, specifying the search criteria requires too much clicking. It should be possible to enter the most widely used criteria in just one tab. So, I would suggest that the object name and type is specified in one text field using the star/question mark syntax, e.g. *.java. This would make the use more intuitive, and also save user some tedious work.
I agree - such a change would be an improvement.
Would be better. A note: the sentence "Furthermore, with the changes in the OpenAPIs/Projects, it is not even necessary to provide a DataLoader (object type in the user terms) in order to give it functionality." is obsolete - DataLoader is still needed.
*** Issue 95062 has been marked as a duplicate of this issue. ***
The Find dialogue has been redesigned (see issue #35255 for details) and file names are now specified the way you describe. The first NetBeans milestone with redesigned Find dialogue is Milestone 10.
Great to see this, thanks many times! I love the new dialog. There are only a couple minor improvements that can be made, which I filed as issue 103791 (enhancement) and issue 106001 (bug). Great job, again.