[
https://issues.apache.org/jira/browse/HBASE-22029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793416#comment-16793416
]
stack edited comment on HBASE-22029 at 3/16/19 5:22 AM:
--------------------------------------------------------
Yeah, HBASE-22052 will fix this. jersey-core is problematic. It was
transitively included from hadoop and polluting our CLASSPATH with an
implementation of a 1.x version of the javax.ws.rs.core.Response Interface from
jsr311-api when we want the javax.ws.rs-api 2.x version. Unfortunately, the
soln. was not simple -- a purge of jersey-core -- because w/o it some mr unit
tests fail. See gore over in HBASE-22052 .
was (Author: stack):
Yeah, HBASE-22029 will fix this. jersey-core is problematic. It was
transitively included from hadoop and polluting our CLASSPATH with an
implementation of a 1.x version of the javax.ws.rs.core.Response Interface from
jsr311-api when we want the javax.ws.rs-api 2.x version. Unfortunately, the
soln. was not simple -- a purge of jersey-core -- because w/o it some mr unit
tests fail. See gore over in HBASE-22029.
> RESTApiClusterManager.java:[250,48] cannot find symbol in hbase-it
> ------------------------------------------------------------------
>
> Key: HBASE-22029
> URL: https://issues.apache.org/jira/browse/HBASE-22029
> Project: HBase
> Issue Type: Sub-task
> Reporter: stack
> Priority: Major
>
> I get this doing a RM build. Can't repro elsewhere.
> Picking up an old jaxrs? See
> https://stackoverflow.com/questions/34679773/extract-string-from-javax-response
> Let me try adding explicit dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
