On Wed, Apr 17, 2019 at 3:19 PM 张铎(Duo Zhang) <palomino...@gmail.com> wrote:
> Do not place site and assembly:single at the same line, it always fails. > First build site, then build assembly, with separated maven commands. This > is a problem from long ago. > > This is my sense Guanghao. I think this a problem apart from hbase-thirdparty, an issue building hbase sir. S > Guanghao Zhang <zghao...@gmail.com> 于2019年4月17日周三 下午10:12写道： > > > Yes. I am building hbase with the new thirdparty 2.2.1... > > > > Peter Somogyi <psomo...@apache.org> 于2019年4月17日周三 下午8:10写道： > > > > > +1 (with note) > > > > > > Checked signature, checksum > > > Built from source on 2.2.1RC0 tag > > > Built HBase master branch with HBASE-22222 patch applied. > > > > > > NOTE: > > > The CHANGES.md file marks 2.2.0 as unreleased. > > > "Release thirdparty-2.2.0 - Unreleased (as of 2019-03-30)" > > > > > > Thanks, > > > Peter > > > > > > On Tue, Apr 16, 2019 at 6:12 PM Stack <st...@duboce.net> wrote: > > > > > > > Please consider the following as the 2.2.1 release of Apache HBase > > > > Thirdparty. It is the first release candidate for your consideration. > > It > > > > has one fix over hbase-thirdparty-2.2.0 to cure an 'interesting' > > > > dependency issue found in 2.2.0 (HBASE-22233). > > > > > > > > Source artifact, signatures, checksums, and changes are available at: > > > > > > > > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty/2.2.1RC0/ > > > > > > > > The release was made against tag 2.2.1RC0. It was signed with my key > > > > 'st...@duboce.net' which can be found here: > > > > > > > > https://dist.apache.org/repos/dist/release/hbase/KEYS > > > > > > > > Maven staging repository is available at: > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachehbase-1304 > > > > > > > > This vote will remain open for at least 72 hours. > > > > > > > > Yours, > > > > Your HBase Release Manager > > > > > > > > > >
