Community
Participate
Working Groups
Some code quality tools allow you to exclude files based on naming conventions via regular expression matches. Typically Rational Application Developer (IBM product based on Eclipse) names generated classes with: 1. an underscore prefix 2. a suffix of "_[a-z0-9]{8}" The unnecessary code and code style options (as two examples) in the compiler Error/Warning settings should not produce warnings on generated classes (if the developer does not wish them to). That way you can click on the root project and see all warnings/errors in the problems view if you have the filter set to show selected element and children. Currently, if you do this, generate classes may show warnings/errors depending on how you have the compiler settings configured.
Any update/thoughts on this one? Thanks.
This enhancement request is not currently in plan for 3.4. To be clear, are you asking for having ways to toggle the compiler severity based on some file name conventions ? Or rather entirely exclude them from the compilation process as the title says ? You can exclude source files today using file patterns (a la Ant), but not regexp.
On a related page, pls see bug 87215
What we would like is to be able to include the files in the compilation process but be able to filter them out of the problems view. Generated files often have errors/warnings when generated as the the framework they are part of has not yet been assembled. Generated files often follow some naming convention. It would be good if we could exclude certain files, using this naming convention, from showing up in the problems view.
Would you still see the problems in the editor if you did open one on some of these derived compilation unit ? Would you expect to find search matches in these ? Would you expect codeassist to suggest completion including these ? Or is it just a mechanism for filtering markers from the problem view - period ?
