[
https://issues.apache.org/jira/browse/HBASE-27501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637249#comment-17637249
]
Bryan Beaudreault commented on HBASE-27501:
-------------------------------------------
I wonder if we need to set {{{}updatePomFile{}}}. According to the docs:
{quote}By default this is only done for projects with packaging other than
{{{}pom{}}}. You may want to also do this for {{pom}} packages projects by
setting this parameter to {{true}} or you can use {{false}} in order to only
generate the flattened POM but never set it as POM file
{quote}
I thought of this because you said it only affects root and
hbase-build-configuration, both of which are pom packaging
> The profiles for some modules are not resolved when packaging
> -------------------------------------------------------------
>
> Key: HBASE-27501
> URL: https://issues.apache.org/jira/browse/HBASE-27501
> Project: HBase
> Issue Type: Bug
> Components: build, pom
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Blocker
> Fix For: 2.6.0, 3.0.0-alpha-4, 2.5.2
>
>
> Found this when trying to make 2.5.2 release, at least the pom for the root
> pom and hbase-build-configuration still contain ${revision} and profiles.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
