[
https://issues.apache.org/jira/browse/HBASE-24223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090155#comment-17090155
]
Duo Zhang commented on HBASE-24223:
-----------------------------------
You are free to use -Dhadoop.profile=3.0 to activate the hadoop-3.0 profile on
branch-2.x, it still works. But on master, since we do not support hadoop 2.x
any more, we changed the activation condition for hadoop-3.0 profile to no
hadoop.profile property, so using -Dhadoop.profile=3.0 does not work on master.
The goal here is to find a general way to activate hadoop-3.0 profile for both
master and branch-2, and using -Phadoop-3.0 is a proper way.
> The -Phadoop-3.0 option does not work on branch-2 and branch-2.3 with JDK11
> ---------------------------------------------------------------------------
>
> Key: HBASE-24223
> URL: https://issues.apache.org/jira/browse/HBASE-24223
> Project: HBase
> Issue Type: Bug
> Components: hadoop3, pom
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.3.0
>
>
> Because we have an enforcer rule which requires the hadoop.profile property
> to be set to 3.0.
> I tried to use requireActiveProfile but it failed when building
> hbase-annotations as in the pom of the module we do not declare a hadoop-3.0
> profile(since it does not depend on hadoop...).
> So we need to find another trick solution.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
