Looks like 3.4.1 hbase-thirdparty is fine after all (my environment was at fault). Sorry for false alarm. S
On Tue, Dec 1, 2020 at 11:33 AM Stack <[email protected]> wrote: > The below release was built with jdk11 it seems. When I tried committing > it to branch-2, I ran into > > java.lang.NoSuchMethodError: > java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer;}} > > (See HBASE-25320) > > I am now working on putting up a 3.4.2 that is 3.4.1 only built w/ jdk8. > Can do a quick vote as soon as it is up and I'll push it out. > > This is a blocker for 2.4.0. > > S > > On Fri, Nov 27, 2020 at 7:52 AM Duo Zhang <[email protected]> wrote: > >> We've just made a new release of the Apache HBase Thirdparty project. >> This project is used by the Apache HBase project to encapsulate a >> number of core dependencies that HBase relies upon ensuring >> that they are properly isolated from HBase downstream users, e.g. >> Google Protocol Buffers, Google Guava, and a few others. >> >> 3.4.1 is just a regular release where we bump the version of some >> dependencies. >> >> The release is available as source at dist.apache.org[1] and as >> artifacts up in Maven central[2]. >> Release notes and Changes can be found at [1]. >> >> The release was tagged rel/3.4.1. >> >> All artifacts are signed with my key 9AD2AE49 which can be found here: >> >> https://dist.apache.org/repos/dist/release/hbase/KEYS >> >> - Your Release Manager >> >> [1] >> https://dist.apache.org/repos/dist/release/hbase/hbase-thirdparty-3.4.1/ >> [2] >> >> https://repository.apache.org/service/local/repositories/releases/content/org/apache/hbase/thirdparty/hbase-thirdparty/3.4.1/ >> >
