089a639724
This is a reapply of a reverted commit. This commit includes HBASE-22059 amendment and subsequent ammendments to HBASE-22052. See HBASE-22052 for full story. jersey-core is problematic. It was transitively included from hadoop and polluting our CLASSPATH with an implementation of a 1.x version of the javax.ws.rs.core.Response Interface from jsr311-api when we want the javax.ws.rs-api 2.x version. M hbase-endpoint/pom.xml M hbase-http/pom.xml M hbase-mapreduce/pom.xml M hbase-rest/pom.xml M hbase-server/pom.xml M hbase-zookeeper/pom.xml Remove redundant version specification (and the odd property define done already up in parent pom). M hbase-it/pom.xml M hbase-rest/pom.xml Exclude jersey-core explicitly. M hbase-procedure/pom.xml Remove redundant version and classifier. M pom.xml Add jersey-core exclusions to all dependencies that pull it in except hadoop-minicluster. mr tests fail w/o the jersey-core so let it in for minicluster and then in modules, exclude it where it causes damage as in hbase-it. |
||
---|---|---|
.. | ||
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 this module -- 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.