ffb2359146
Increment version in poms with ``` $ mvn org.codehaus.mojo:versions-maven-plugin:2.7:set -DnewVersion=2.4.0-SNAPSHOT -DgenerateBackupPoms=false ``` Verified no dangling references with ``` $ find . -iname '*pom.xml' -exec grep -n '2.3.0-SNAPSHOT' {} + ``` Verified build with ``` $ JAVA_HOME=/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home mvn clean package -DskipTests $ JAVA_HOME=/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home mvn clean package -DskipTests -Dhadoop.profile=3.0 ``` Signed-off-by: Jan Hentschel <jan.hentschel@ultratendency.com> |
||
---|---|---|
.. | ||
src | ||
README.txt | ||
pom.xml |
README.txt
ON PROTOBUFS This maven module has core protobuf definition files ('.protos') used by hbase REST that ship with hbase core including tests. The protobuf version they use can be distinct from that used by HBase internally since HBase started shading its protobuf references. REST Endpoints have no access to the shaded protobuf hbase uses. They do have access to the content of hbase-protocol -- the .protos found in here -- but avoid using as much of this as you can as it is liable to change. Generation of java files from protobuf .proto files included here is done as part of the build.