[
https://issues.apache.org/jira/browse/HBASE-28930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated HBASE-28930:
--------------------------------
Description:
Unless there is some specific reason, all dependency versions should be set in
DependencyManage sections.
Right now we at least some Hadoop dependencies where the versions are
redundantly set directly in the Dependency entries.
We should also consistently set hadoop.version from the hadoop3 profiles in the
modules that have them. (I think that those aren't relevant in branch-3+, but
we should either set them consistently, or just remove them outside branch-2.x)
was:
Unless there is some specific reason, all dependency versions should be set in
DependencyManage sections.
Right now we at least some Hadoop dependencies where the versions are set
directly in the Dependency entries.
We should also consistently set hadoop.version from the hadoop3 profiles in the
modules that have them. (I think that those aren't relevant in branch-3+, but
we should either set them consistently, or just remove them outside branch-2.x)
> Clean up explicit depency versions in poms
> ------------------------------------------
>
> Key: HBASE-28930
> URL: https://issues.apache.org/jira/browse/HBASE-28930
> Project: HBase
> Issue Type: Bug
> Reporter: Istvan Toth
> Priority: Major
>
> Unless there is some specific reason, all dependency versions should be set
> in DependencyManage sections.
> Right now we at least some Hadoop dependencies where the versions are
> redundantly set directly in the Dependency entries.
> We should also consistently set hadoop.version from the hadoop3 profiles in
> the modules that have them. (I think that those aren't relevant in branch-3+,
> but we should either set them consistently, or just remove them outside
> branch-2.x)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
