Community
Participate
Working Groups
Build Identifier: M20090917-0800 Problem: if you use maven or other build tools to build your project, many resources in a project are derived, but eclipse does not know that they are derived. The consequence is that if you enter a file name in the "Open Resource" dialog, this file might appear many times - and you have to search for the occurrence that is in an actual source directory. I'd suggest extending the configuration of the "Open Resource" dialog by a filter with a list of ignored directory names / directory and file patterns whose contents should not be shown. Often that would be "target" if you are using maven, or "bin" if you are using ant. Reproducible: Always Steps to Reproduce: Open a project that is built with maven in eclipse, but leave the eclipse build directory to .eclise_classes or something to avoid conflicts between maven builds and eclipse builds. (That way you can execute a maven build without disturbing eclipse.) Then open the "Open Resource" dialog and start to type a class name. Many matches are shown that are not relevant: class files, in some maven configurations also source files that are copied to the target directory by some maven plugin.
There is a 'Show Derived Resources' in the pull down menu of the Open Resources dialog. Does that help?
(In reply to comment #1) > There is a 'Show Derived Resources' in the pull down menu of the Open Resources > dialog. Does that help? I know; but that helps only partially. If you configure eclipse such that it uses target/classes and target/test-classes as output directories, the class files that maven generates in these directories are not shown anymore. But this is not always desirable, and it does not help against other files maven puts into the target directory. That can be very many if you have overlay WARs etc. In the project I am currently working on many files (mostly JSP) are shown 6 times - once in the actual source directory, and 5 more times in the target directories of several other projects. So I say: Help! :-) One more thing: in some cases you will have (generated) sources as well as derived resources in the maven target directory. So one might want resources to show up that match the filter (i.e. target/*) but are contained in a source folder configured in that project (i.e. target/generated-sources/).
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
