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.
