I'll pull this in today as well. Like you say, this shouldn't have more issues -- we'll find out soon :)

On 3/17/18 4:20 PM, Mike Drob wrote:
Yea, I'm not concerned about commons-collections3 v commons-collections4 or
whatever the latest libs may be. I'm more concerned about collections4.1 v
4.2 or something like that, and I really hope that we don't have to redo
our import statements for each minor release.

On Fri, Mar 16, 2018 at 5:58 PM, Josh Elser <els...@apache.org> wrote:

Yeah, all of the commons-* projects worry me.

Recently, commons-math and commons-collections introduced different GAV
and java-package which give me some hope that they'll be OK going forward.

Not sure about IO, crypto, and lang..


On 3/16/18 6:19 PM, Mike Drob wrote:

commons-collections? I don't know what their minor version compatibility
story is, but that seems like a place that this could easily come up again
in the not so distant future.

On Fri, Mar 16, 2018 at 4:46 PM, Andrew Purtell <apurt...@apache.org>
wrote:

+1 on protobuf. Any chance we can get a vote period long enough to do a
comparison perf / GC test? I can help.

On Fri, Mar 16, 2018 at 2:41 PM, Stack <st...@duboce.net> wrote:

Probably too risky to do at this stage in the game but protobuf? We're on
3.3.1. Latest is 3.5.1 [1]: "Various performance optimizations." And

Guava

is 24.1 now. We're on 22.

St.Ack
1. https://github.com/google/protobuf/releases


On Fri, Mar 16, 2018 at 1:47 PM, Josh Elser <els...@apache.org> wrote:

Give a shout if there's anything that you all think would be good to
include in a new hbase-thirdparty release for HBase 2.0.

I'm pulling in commons-cli as per https://issues.apache.org/jira
/browse/HBASE-20201.

If there's more that should come in, please let me know!





--
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
     - A23, Crosstalk




Reply via email to