[
https://issues.apache.org/jira/browse/HBASE-24347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124709#comment-17124709
]
Guanghao Zhang commented on HBASE-24347:
----------------------------------------
{quote}I think much of the CI refactoring I did to support JDK11 didn't go back
to branch-2.2 since it wasn't to be supported there. I think that would be the
primary reason for differences.
{quote}
Got it. Thanks for explanation.
> Hadoop2&Hadoop3 profiles are both active when pre-commit PR builds run
> ----------------------------------------------------------------------
>
> Key: HBASE-24347
> URL: https://issues.apache.org/jira/browse/HBASE-24347
> Project: HBase
> Issue Type: Sub-task
> Components: build
> Reporter: Michael Stack
> Assignee: Josh Elser
> Priority: Major
> Fix For: 2.3.0, 2.4.0, 2.2.6
>
> Attachments: HBASE-24280.001.branch-2.3.patch,
> HBASE-24280.001.branch-2.patch
>
>
> We need the magic done in the parent out in our precommit builds too. See how
> https://github.com/apache/hbase/pull/1664 fails in hbase-rest w/ complaint
> about jersey; this is a symptom of double hadoop2+hadoop3 profile activation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
