hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14876) Provide maven archetypes
Date Fri, 11 Dec 2015 21:34:46 GMT

    [ https://issues.apache.org/jira/browse/HBASE-14876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053600#comment-15053600
] 

Nick Dimiduk commented on HBASE-14876:
--------------------------------------

Thanks for picking this up, [~daniel_vimont]. I was expecting we'd include the archetypes
in our repository as maven submodules of the root-level HBase maven project. That way they
stay in lock-step with the API's they're designed to consume. Is that possible? Would you
mind attaching patches that introducing your work in that form? They'll be easier for folks
to review.

> Provide maven archetypes
> ------------------------
>
>                 Key: HBASE-14876
>                 URL: https://issues.apache.org/jira/browse/HBASE-14876
>             Project: HBase
>          Issue Type: New Feature
>          Components: build, Usability
>            Reporter: Nick Dimiduk
>            Assignee: Daniel Vimont
>              Labels: beginner
>         Attachments: 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)

Mime
View raw message