This depends on the parser. Most of the parsers create files with absolute filenames. If the parser produces relative paths then the absolute paths are determined after the filter operation.
But it should be possible to move the filtering after the expansion. Please file a new feature request in Jira. Am 28.07.2014 um 21:37 schrieb Jon Schewe <jpsch...@mtu.net>: > It seems that the problem is that the filter is not done on the absolute path > to the file, but rather the filename fragment that shows up in the warning. > This makes it very difficult to ignore all warnings for a given directory. I > need to list each file in the directory explicitly. > > > On Mon, Jul 28, 2014 at 10:14 AM, Jon Schewe <jpsch...@mtu.net> wrote: > I see that under the advanced section of the compiler warnings module there > is an option to ignore files based on their absolute file path. Does this > work to filter warnings found in the console output or only when scanning > files? > > I have a directory at the top of my workspace named "log4cxx/source". I don't > want to be notified of any warnings in that directory. The warnings are found > in the console output. I have tried the following filters, all without success > log4cxx/source > .*/log4cxx/source/.* > log4cxx/source/** > > Has anyone gotten this type of filtering to work? > > Thanks. > > -- > http://mtu.net/~jpschewe > > > > > -- > http://mtu.net/~jpschewe > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
