[
https://issues.apache.org/jira/browse/YETUS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772115#comment-16772115
]
Allen Wittenauer commented on YETUS-794:
----------------------------------------
Yup: it's definitely not comprehensive. There's a fine line here, I think,
that documentation might be the only way out. In my head, we would want the
build system to fail during a compile, but we don't necessarily want the static
analyzers to throw a fit because the provided source has an excess tab or an
@author tag. There's also the problem that this doesn't configure every static
analyzer because it's simply too hard (e.g., checkstyle, jshint, etc).
If you've got a recommendation on how to change the text, I'd be very
appreciative. What's written currently is like my 4th pass. haha.
FWIW, I'm using this feature daily with repos that contain C, Go, Python, and
bash where we have many directories of vendor-provided bits and even Linux
kernel patch files. I haven't tried it with anything Java-based. It'd be
great to for someone to try that out and see if anything was missed.
> exclusion support
> -----------------
>
> Key: YETUS-794
> URL: https://issues.apache.org/jira/browse/YETUS-794
> Project: Yetus
> Issue Type: New Feature
> Components: Test Patch
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Major
> Attachments: YETUS-794.00.patch
>
>
> Some paths in the source tree may come from 3rd parties that, for various
> reasons, may fail tests. It would be useful to have a way to ignore such
> paths when reporting on errors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
