From 361846220b62c887d2255c76b19e971649e264a8 Mon Sep 17 00:00:00 2001 From: Mike Drob Date: Fri, 13 Apr 2018 09:44:59 -0500 Subject: [PATCH] HBASE-20410 update protoc to 3.5.1-1 for rhel6 --- hbase-protocol-shaded/pom.xml | 2 +- src/main/asciidoc/_chapters/developer.adoc | 12 ------------ 2 files changed, 1 insertion(+), 13 deletions(-) diff --git a/hbase-protocol-shaded/pom.xml b/hbase-protocol-shaded/pom.xml index 25443e1830..e9d6f319c0 100644 --- a/hbase-protocol-shaded/pom.xml +++ b/hbase-protocol-shaded/pom.xml @@ -34,7 +34,7 @@ - 3.5.1 + 3.5.1-1 diff --git a/src/main/asciidoc/_chapters/developer.adoc b/src/main/asciidoc/_chapters/developer.adoc index 9d9f564657..9e76f85e8a 100644 --- a/src/main/asciidoc/_chapters/developer.adoc +++ b/src/main/asciidoc/_chapters/developer.adoc @@ -433,18 +433,6 @@ convenience; however, the plugin may not be able to retrieve appropriate binarie on a platform where protoc fails, you will have to compile protoc from source, and run it independent of our maven build. You can disable the inline code generation by specifying `-Dprotoc.skip` in your maven arguments, allowing your build to proceed further. -A similar failure relates to the stock CentOS 6 docker image providing a too old version of glibc for the version of protoc that we use. -In this case, you would have to install glibc 2.14 and protoc 3.5.1 manually, then execute something like: - -[source,bourne] ----- -cd hbase-protocol-shaded -LD_LIBRARY_PATH=/opt/glibc-2.14/lib protoc \ - --proto_path=src/main/protobuf \ - --java_out=target/generated-sources/protobuf/java \ - src/main/protobuf/*.proto ----- - [NOTE] If you need to manually generate your protobuf files, you should not use `clean` in subsequent maven calls, as that will delete the newly generated files. -- 2.16.1