[
https://issues.apache.org/jira/browse/HBASE-24280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17097136#comment-17097136
]
Sean Busbey commented on HBASE-24280:
-------------------------------------
can we update all the branches to use maven profile activation instead of a
property?
some time ago we had to duplicate defaults in the main project properties for
whatever properties get defined in these profiles, because some non-maven
downstream build system another ignores profile activation (sbt? gradle? who
knows).
We could maybe formalize that with some comments that mark which properties
are for the default hadoop profile. Then it would be fine to give no profile or
to give {{-Phadoop-3.0}} on any branch.
> TestSecureRESTServer started failing in nightlies for Hadoop3
> -------------------------------------------------------------
>
> Key: HBASE-24280
> URL: https://issues.apache.org/jira/browse/HBASE-24280
> Project: HBase
> Issue Type: Bug
> Reporter: Josh Elser
> Assignee: Istvan Toth
> Priority: Major
> Fix For: 2.3.0
>
> Attachments: HBASE-24280.master.001.patch,
> TEST-org.apache.hadoop.hbase.rest.TestSecureRESTServer.xml
>
>
> [~ndimiduk] pointed out that, after this change went in, TestSecureRESTServer
> started failing with Hadoop3 on branch-2.3
> https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/56/
> Of course, I ran this with 1.8.0_241 and Maven 3.6.33 and it passed :) {{mvn
> clean package -Dtest=TestSecureRESTServer -Dhadoop.profile=3.0
> -DfailIfNoTests=false}}
> FYI [~stoty] in case you can repro a failure and want to dig in. Feel free to
> re-assign.
> It looks like we didn't have a nightly run of branch-2.2 due to docker
> container build issues. Will be interesting to see if it fails there. It did
> not fail the master nightly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
