You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Josh Elser (Jira)" <ji...@apache.org> on 2020/03/26 20:26:00 UTC

[jira] [Commented] (HBASE-24066) Expose shaded clients through WebUI as Maven repository

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

Josh Elser commented on HBASE-24066:
------------------------------------

{quote}The idea here is that we can use embedded Jetty to "fake" out a Maven repository that users can put in their client applications
{quote}
Click through to the pull request to see an example user application.

> Expose shaded clients through WebUI as Maven repository
> -------------------------------------------------------
>
>                 Key: HBASE-24066
>                 URL: https://issues.apache.org/jira/browse/HBASE-24066
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>
> Props to [~busbey] for this idea.
> We have a number of shaded jars which are (largely) sufficient for launching any Java application against HBase. However, if users have multiple versions of HBase in their organization, it might be confusing to know "which client" do I need to use? Can we expose our shaded clients from HBase in such a way that build tools can just ask HBase for the client jars they should use?
> The idea here is that we can use embedded Jetty to "fake" out a Maven repository that users can put in their client applications. We have no extra burden from HBase because we already are packaging these jars. I'll link an example Maven application which uses this "feature".



--
This message was sent by Atlassian Jira
(v8.3.4#803005)