You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2023/03/06 12:49:00 UTC

[jira] [Updated] (PHOENIX-6893) Remove explicit dependency declaration on hbase-thirdparty artifacts

     [ https://issues.apache.org/jira/browse/PHOENIX-6893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Istvan Toth updated PHOENIX-6893:
---------------------------------
    Summary: Remove explicit dependency declaration on hbase-thirdparty artifacts  (was: Remove explicit dependency declaration on hbase-thirdparty)

> Remove explicit dependency declaration on hbase-thirdparty artifacts
> --------------------------------------------------------------------
>
>                 Key: PHOENIX-6893
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6893
>             Project: Phoenix
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 5.2.0, 5.1.3
>            Reporter: Istvan Toth
>            Assignee: Istvan Toth
>            Priority: Major
>
> Hbase has bumped hbase-thirdparty to 4.1.4 on both branch-2.4 and branch-2.5
> -Update the versions in Phoenix.-
> -This may cause problems when building with older HBase patch releases, but that will have to be handled by specifying both the hbase and hbase-thirdparty versions, as we cannot realisticaly maintain hbase-thirdparty version mapping for all Hbase point releases.-
> Instead of trying to keep up with the frequent version updates, just remove the direct dependency declaration from the poms, and rely on the transitive dependencies.
> We need to tell maven-dependency-plugin not complain about it.
> We also need to switch to a different exclusion method when shading phoenix-server, as the current method requires setting the version.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)