[
https://issues.apache.org/jira/browse/HBASE-14877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102131#comment-15102131
]
Sean Busbey commented on HBASE-14877:
-------------------------------------
no worries! always happy to help new folks to HBase and downstream users of
Yetus, so this is a two-for-one. ;)
{quote}
The "findbugs" step is failing in the master branch before my patch is applied.
The message says that "no findbugs output file" is found in the root's ./target
subdirectory. As far as I can see, the lack of findbugs output is to be
expected, since there is NO java code in the root's ./src subdirectory for
findbugs to inspect.
{quote}
Yes, yetus by default reports on the health of the repository both before and
after a given patch. this is both so that folks can generally be aware of how
the code base is doing (for example, there are now hbase jiras for fixing the
extent findbugs errors in some modules) and so that patches that are fixing
findbugs errors are obvious.
The particular bug of "no java code gives a findbugs -1" is YETUS-271, which
will be fixed in the next release. If all of the modules that are failing
findbugs have no java code, then I'd say they can safely be ignored.
> maven archetype: client application
> -----------------------------------
>
> Key: HBASE-14877
> URL: https://issues.apache.org/jira/browse/HBASE-14877
> Project: HBase
> Issue Type: Sub-task
> Components: build, Usability
> Affects Versions: 2.0.0
> Reporter: Nick Dimiduk
> Assignee: Daniel Vimont
> Labels: archetype, beginner, maven
> Attachments: HBASE-14877-v2.patch, HBASE-14877-v3.patch,
> HBASE-14877.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
