[
https://issues.apache.org/jira/browse/HBASE-27065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542695#comment-17542695
]
Andrew Kyle Purtell commented on HBASE-27065:
---------------------------------------------
Something asked about on the PR by [~weichiu]: I'm not sure why leveldb-jni is
an issue now either. Perhaps there was a version increment, and anyway there is
an architectural difference. On x86_64 the groupId is fusesource. On aarch64 it
is openlabtesting. The license metadata in the POMs of these different
arch-specific releases could vary. My build and test hosts are aarch64 so I may
be one of the first to notice.
> Build against Hadoop 3.3.3
> --------------------------
>
> Key: HBASE-27065
> URL: https://issues.apache.org/jira/browse/HBASE-27065
> Project: HBase
> Issue Type: Bug
> Components: build
> Affects Versions: 2.5.0
> Reporter: Andrew Kyle Purtell
> Assignee: Andrew Kyle Purtell
> Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-3
>
>
> When building against Hadoop 3.3.3 and any future version of Hadoop
> incorporating reload4j, the new Enforcer rule we have active in branch-2.5
> and up to exclude other logging frameworks besides log4j2 will trigger. We
> need to add exclusions to prevent that from happening so the build will
> succeed.
> Tested with {{mvn clean install assembly:single -DskipTests
> -Dhadoop-three.version=3.3.3}} on master branch and with {{mvn clean install
> assembly:single -DskipTests -Dhadoop.profile=3.0
> -Dhadoop-three.version=3.3.3}} on branch-2.5.
> I also needed to exclude leveldbjni-all via hadoop-hdfs to avoid a LICENSE
> file generation error. hadoop-hdfs is messy and exports this among findbugs
> and other clutter. Anyway, better to exclude something we do not require than
> add an unnecessary supplemental model.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
