9927c2e14a
* rely on git plumbing commands when checking if we've built the site for a particular commit already * switch to forcing '-e' for bash * add command line switches for: path to hbase, working directory, and publishing * only export JAVA/MAVEN HOME if they aren't already set. * add some docs about assumptions * Update javadoc plugin to consistently be version 3.0.0 * avoid duplicative site invocations on reactor modules * update use of cp command so it works both on linux and mac * manually skip enforcer plugin during build * still doing install of all jars due to MJAVADOC-490, but then skip rebuilding during aggregate reports. * avoid the pager on git-diff by teeing to a log file, which also helps later reviewing in the case of big changesets. Signed-off-by: Michael Stack <stack@apache.org> Signed-off-by: Misty Stanley-Jones <misty@apache.org> Conflicts: hbase-backup/pom.xml hbase-spark-it/pom.xml |
||
|---|---|---|
| .. | ||
| src/main | ||
| README.txt | ||
| pom.xml | ||
README.txt
ON PROTOBUFS
This maven module has core protobuf definition files ('.protos') used by hbase
Coprocessor Endpoints that ship with hbase core including tests. Coprocessor
Endpoints are meant to be standalone, independent code not reliant on hbase
internals. They define their Service using protobuf. The protobuf version
they use can be distinct from that used by HBase internally since HBase started
shading its protobuf references. 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.