[
https://issues.apache.org/jira/browse/HBASE-14877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101157#comment-15101157
]
Daniel Vimont commented on HBASE-14877:
---------------------------------------
I'm in the process of making further adjustments to the findbugs plugin
overrides that I'm putting into hbase/hbase-archetypes/pom.xml, but while I'm
doing that, I think it's worth noting a peculiarity in the
precommit-build-output above:
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.
After my "v2" patch is applied, similar findbugs "failures" are reported for
new subprojects that also contain no java code in their ./src subdirectory:
hbase-archetypes and hbase-archetypes/hbase-archetype-builder.
> 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.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
