[
https://issues.apache.org/jira/browse/HBASE-14876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097680#comment-15097680
]
Daniel Vimont commented on HBASE-14876:
---------------------------------------
Okay, I see the origin of the prob in the 'findbugs' plugin configuration in
hbase/pom.xml:
<configuration>
<excludeFilterFile>${project.basedir}/../dev-support/findbugs-exclude.xml</excludeFilterFile>
...
</configuration>
Obviously, this was set up under the assumption that all hbase subprojects
would only be one level down in the directory hierarchy, whereas the
infrastructure that I've set up for archetypes has the projects two levels down
(e.g., hbase-archetypes/hbase-client-project).
I will now ponder what to do about this...
> Provide maven archetypes
> ------------------------
>
> Key: HBASE-14876
> URL: https://issues.apache.org/jira/browse/HBASE-14876
> Project: HBase
> Issue Type: New Feature
> Components: build, Usability
> Affects Versions: 2.0.0
> Reporter: Nick Dimiduk
> Assignee: Daniel Vimont
> Labels: beginner, maven
> Attachments: HBASE-14876-v2.patch, HBASE-14876.patch,
> archetype_prototype.zip, archetype_prototype02.zip,
> archetype_shaded_prototype01.zip
>
>
> To help onboard new users, we should provide maven archetypes for hbase
> client applications. Off the top of my head, we should have templates for
> - hbase client application with all dependencies
> - hbase client application using client-shaded jar
> - mapreduce application with hbase as input and output (ie, copy table)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
