You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2022/02/26 06:22:00 UTC

[jira] [Resolved] (HBASE-26591) [hbase-thirdparty] Make a 4.0.1 release for hbase-thirdparty

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

Duo Zhang resolved HBASE-26591.
-------------------------------
    Resolution: Fixed

> [hbase-thirdparty] Make a 4.0.1 release for hbase-thirdparty
> ------------------------------------------------------------
>
>                 Key: HBASE-26591
>                 URL: https://issues.apache.org/jira/browse/HBASE-26591
>             Project: HBase
>          Issue Type: Umbrella
>          Components: community, thirdparty
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>
> Copy the content in mailing list here
> {noformat}
> Oh, when backporting to branch-2, I found that there is a serious problem with this release.
> We do not include the proto files in protobuf-java jar, I think this is a side effect of HBASE-26496.
> And on the master branch, hbase-shaded-protobuf also pulls in protobuf-java 3.19.1 dependency so everything is fine. But for branch-2, we will need to depend on protobuf 2.5.0 then the compilation is broken.
> Anyway, we should include the proto files in hbase-shaded-protobuf,  and also we should not pull in the original protobuf-java dependency.
> Let me fix this and do a 4.0.1 release.
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)