Community
Participate
Working Groups
It is common to want to exclude all files of a certain type from a source folder's output folder, e.g., all *.html files, regardless of where in the source tree the *.html file exists. Right now, it seems the best one can do is build an exclusion filter for each level of a source tree. e.g., /packagename/*.html, /packagename/*/*.html, /packagename/*/*/*.html ... Why not allow simply *.html and have exclude all *.html files regardless of where they are in the source folder. Or, as an alternative, */*.html with no leading slash could represent any number of levels in the source tree.
It should work using "**/*.html" as an exclusion pattern, but I agree with you this should be equivalent to "*.html". Currently, we transform the relative exclusion pattern into a workspace relative exclusion pattern: "*.html" --> "/Proj/src/*.html". If the exclusion pattern isn't absolute, we should rather append "**/*.html". Need to investigate.
Actually, originally we had implemented the exclusion patterns to be exactly doing so, and we switched to the current story. Cannot remember why we did so.
I take my previous comments back. Also see bug 29761 which explains why we did change our original (wrong) behavior. Ant patternset rules are not treating 'a' as '**/a' by default. Only trailing separator is special ('a/' is equivalent to 'a/**'). Thus you should explicitly qualify your exclusion pattern with a leading '**/'.
When I submitted the enhancement request, I was not aware of the **/... option.Maybe this should be closed as the functionality is already available. I see now that the option is described in the field help, but that was not read by my screen reader. The 5/28 build allows field help and error messages to be tabbed to, making them accessible to a screen reader. but for some reason that feature does not work in the exclusion filter dialog. I will report that in that feature's record.
