In our environment the build tool creates a number of symlinks to parent directories creating recursive directory structures. This play's havoc with Ant's DirectoryScanner used by the FileFinder in the warnings-ng-plugin. The default protections in DirectoryScanner (limit to traversing 5 levels of symlinks) aren't sufficient, given the number of files in our output directory, to prevent the jenkins agent from running out of memory. Preventing symlink traversal altogether (see patch) fixes the problem.

However I suspect this may break some users, would it be possible to have a configuration option next to the fileset pattern to be scanned to include a checkbox to disable traversing symlinks.

We've already tried moving the appropriate files to a different directory structure, but the FindBugs/SpotBugs file searching will search for the originating Java files after getting the main analysis records, which causes to break as well (uses the same FileFinder).