[
https://issues.apache.org/jira/browse/HBASE-21758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749107#comment-16749107
]
Andrew Purtell edited comment on HBASE-21758 at 1/22/19 8:30 PM:
-----------------------------------------------------------------
Huh. I'm not able to get any successful build with -Dhadoop.profile=3.0 with
Maven 3.6. Build errors out in hbase-common, missing classes Configuration,
Groups, Job, etc. It's like the hadoop-common and hadoop-mapreduce-client-core
dependencies defined in the profiles are pulled in for things like
dependency:tree but not actually for the compiler. Compiler errors out with
missing classes from those artifacts. Anyone seen this before? ([~busbey] -
comment on another JIRA suggests you might have tried it)
If I move the dependency specifications for hadoop-common and
hadoop-mapreduce-client-core out of the conditional build profiles (unifying
the exclusions), then builds with 2.0 and 3.0 profiles both work. Something
about the conditional specification of these dependencies is not working right.
In most modules it looks like the build profile for hadoop-2.0 and hadoop-3.0
are mostly the same so could be refactored without breaking the hadoop-2.0
build but I don't want to do it without understanding better what is going on.
Not a Maven expert.
was (Author: apurtell):
Huh. I'm not able to get any successful build with -Dhadoop.profile=3.0 with
Maven 3.6. Build errors out in hbase-common, missing classes Configuration,
Groups, Job, etc. It's like the hadoop-common and hadoop-mapreduce-client-core
dependencies defined in the profiles are pulled in for things like
dependency:tree but not actually for the compiler. Compiler errors out with
missing classes from those artifacts. Anyone seen this before? ([~busbey] -
comment on another JIRA suggests you might have tried it)
If I move the dependency specifications out of the profiles (unifying the
exclusions), then builds with 2.0 and 3.0 profiles both work. Something about
the conditional specification of these dependencies is not working right. In
most modules it looks like the build profile for hadoop-2.0 and hadoop-3.0 are
mostly the same so could be refactored without breaking the hadoop-2.0 build
but I don't want to do it without understanding better what is going on. Not a
Maven expert.
> Update hadoop-three.version on branch-1 to 3.0.3
> ------------------------------------------------
>
> Key: HBASE-21758
> URL: https://issues.apache.org/jira/browse/HBASE-21758
> Project: HBase
> Issue Type: Task
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Trivial
> Fix For: 1.5.0
>
> Attachments: HBASE-21758-branch-1.patch
>
>
> Sync the branch-1 POM with master and branch-2 with respect to the default
> version of {{hadoop-three.version}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
