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

Hadoop QA commented on HBASE-22052:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  6s{color} 
| {color:red} HBASE-22052 does not apply to master. Rebase required? Wrong 
Branch? See https://yetus.apache.org/documentation/0.8.0/precommit-patchnames 
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-22052 |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/16511/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was automatically generated.



> pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove 
> redunant version specifications
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-22052
>                 URL: https://issues.apache.org/jira/browse/HBASE-22052
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>             Fix For: 2.2.0, 2.0.5, 2.1.4
>
>         Attachments: HBASE-22052.2.1.003.addendum1.txt, 
> HBASE-22052.branch-2.0.001.patch, HBASE-22052.branch-2.0.002.patch, 
> HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.003.patch, 
> HBASE-22052.branch-2.0.004.patch, HBASE-22052.branch-2.1.001.patch, 
> HBASE-22052.branch-2.1.002.patch, HBASE-22052.branch-2.1.003.patch, 
> HBASE-22052.branch-2.2.001.patch, HBASE-22052.branch-2.2.002.patch
>
>
> Working on HBASE-22029, where we fail compile of hbase-it module four hours 
> into an RC build, it looks like transitive include of jersey-core is the 
> culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue 
> is about having hadoop2 profile and hadoop3 profiles match around jersey-core 
> treatment. Some miscellaneous cleanups are also done.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to