[
https://issues.apache.org/jira/browse/YETUS-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732714#comment-15732714
]
Peter Vary commented on YETUS-471:
----------------------------------
{quote}
We could ask maven to list the configured source directories, but do we want to
head down that route?
{quote}
I think it might pose another problem - Do we want to check the generated codes
with findbugs as well, or we want to make it configurable? I think it would
open Pandora's box as well...
What are the drawbacks of making the {{findbugs_maven_skipper}} function
replaceable? How hard is to do that? If I understand well how Yetus works this
will allow the personality to overwrite this function, and allow the user to
decide what to run / when to check.
> Add possibility to configure Findbugs source folders
> ----------------------------------------------------
>
> Key: YETUS-471
> URL: https://issues.apache.org/jira/browse/YETUS-471
> Project: Yetus
> Issue Type: Improvement
> Components: Test Patch
> Affects Versions: 0.3.0
> Reporter: Peter Vary
> Assignee: Peter Vary
> Attachments: YETUS-471.00.patch, YETUS-471.01.patch,
> YETUS-471.02.patch
>
>
> Trying to add yetus as a pre-commit test for Hive (see HIVE-15051)
> Findbugs plugin currently expects the project structure to be the standard
> maven one (/src/main/java, /src/test/java). In Hive some of the modules have
> a different file layout. It would be good to have a parameter introduced to
> enable changes in checking directories.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
