[
https://issues.apache.org/jira/browse/HBASE-19170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244475#comment-16244475
]
stack commented on HBASE-19170:
-------------------------------
This issue wants jetty in third-party... if we make a new third-party, might
want to do the jetty at same time.
> [hbase-thirdparty] Change the relocation offset of shaded artifacts
> -------------------------------------------------------------------
>
> Key: HBASE-19170
> URL: https://issues.apache.org/jira/browse/HBASE-19170
> Project: HBase
> Issue Type: Bug
> Affects Versions: thirdparty-1.0.1
> Reporter: Jerry He
> Assignee: Mike Drob
> Priority: Critical
> Fix For: 2.0.0-beta-1, thirdparty-1.0.2
>
> Attachments: HBASE-19170.patch, HBASE-19170.v2.patch
>
>
> On the dev@hbase list, we conclude that we need to change the relocation
> offset in hbase-thirdparty to avoid shading conflicts with the other hbase
> shaded components (hbase-shaded-client and hbase-shaded-mapreduce components).
> https://lists.apache.org/thread.html/1aa5d1d7f6d176df49e72096926b011cafe1315932515346d06e8342@%3Cdev.hbase.apache.org%3E
> The suggestion is to use "o.a.h.hbase.thirdparty" in hbase-thirdparty to
> differentiate between "shaded" for downstream of us vs "thirdparty" for our
> internal use.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
