[
https://issues.apache.org/jira/browse/HBASE-28883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884589#comment-17884589
]
Nick Dimiduk commented on HBASE-28883:
--------------------------------------
See also the discussion on
https://github.com/apache/hbase/pull/6295#discussion_r1775002522
> Manage hbase-thirdparty transitive dependencies via BOM pom
> -----------------------------------------------------------
>
> Key: HBASE-28883
> URL: https://issues.apache.org/jira/browse/HBASE-28883
> Project: HBase
> Issue Type: Task
> Components: build, thirdparty
> Reporter: Nick Dimiduk
> Priority: Major
>
> Despite the intentions to the contrary, there are several places where we
> need the version of a dependency managed in hbase-thirdparty to match an
> import in the main product (and maybe also in our other repos). Right now,
> this is managed via comments in the poms, which read "when this changes
> there, don't for get to update it here...". We can do better than this.
> I think that hbase-thirdparty could publish a BOM pom file that can be
> imported into any of the downstream hbase projects that make use of that
> release of hbase-thirdparty. That will centralize management of these
> dependencies in the hbase-thirdparty repo.
> This blog post has a nice write-up on the idea,
> https://www.garretwilson.com/blog/2023/06/14/improve-maven-bom-pattern
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
