fb537fe736
Do a pass with dependency:analyze; remove unused and explicity list the dependencies we exploit. Remove the parent dependencies set which had junit, mockito, log4j, and findbugs annotations (had to put junit back temporarily in subsequent version of this patch TODO). Listing in parent set meant these libs were dependencies for all modules which in practice was not the case. Edited all modules so those that need any from this parent set now do explicit listing. Ran the dependency:analyze over the project. Acted on most suggested removals and requests for explicit listing. Some grey areas remain around transitives that come in with hadoop -needs better excludes, another project- and that the dependency:analyze tool is not always accurate in its reporting. |
||
|---|---|---|
| .. | ||
| src | ||
| README.txt | ||
| pom.xml | ||
README.txt
ON PROTOBUFS
This maven module has 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.