ee84a8f243
* modify the jar checking script to take args; make hadoop stuff optional * separate out checking the artifacts that have hadoop vs those that don't. * * Unfortunately means we need two modules for checking things * * put in a safety check that the support script for checking jar contents is maintained in both modules * * have to carve out an exception for o.a.hadoop.metrics2. :( * fix duplicated class warning * clean up dependencies in hbase-server and some modules that depend on it. * allow Hadoop to have its own htrace where it needs it * add a precommit check to make sure we're not using old htrace imports Conflicts: hbase-backup/pom.xml hbase-checkstyle/src/main/resources/hbase/checkstyle-suppressions.xml Signed-off-by: Mike Drob <mdrob@apache.org> |
||
|---|---|---|
| .. | ||
| 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.