eacbdb061e
Update plugins in main and subprojects Unified versions to use variable instead of direct values Affected plugins: - apache-rat-plugin 0.11 -> 0.12 - asciidoctor-maven-plugin 1.5.2.1 -> 1.5.5 - asciidoctorj-pdf 1.5.0-alpha.6 -> 1.5.0-alpha.15 - build-helper-maven-plugin 1.9.1 -> 3.0.0 - buildnumber-maven-plugin 1.3 -> 1.4 - exec-maven-plugin 1.2.1/1.4.0 -> 1.6.0 - extra-enforcer-rules 1.0-beta-3 -> 1.0-beta-6 - findbugs-maven-plugin 3.0.0 -> 3.0.4 - jamon-maven-plugin 2.4.1 -> 2.4.2 - maven-bundle-plugin 2.5.3 -> 3.3.0 - maven-compiler-plugin 3.2/3.5.1 -> 3.6.1 - maven-eclipse-plugin 2.9 -> 2.10 - maven-shade-plugin 2.4.1 -> 3.0.0 - maven-surefire-plugin 2.18.1 -> 2.20 - maven-surefire-report-plugin 2.7.2 -> 2.20 - scala-maven-plugin 3.2.0 -> 3.2.2 - spotbugs 3.1.0-RC1 -> 3.1.0-RC3 - wagon-ssh 2.2 -> 2.12 - xml-maven-plugin 1.0 -> 1.0.1 - maven-assembly-plugin 2.4 -> 2.6(inherited) - maven-dependency-plugin 2.4 -> 2.10 (inherited) - maven-enforcer-plugin 1.3.1 -> 1.4.1 (inherited) - maven-javadoc-plugin 2.10.3 -> 2.10.4 (inherited) - maven-resources-plugin 2.7 (inherited) - maven-site-plugin 3.4 -> 3.5.1 (inherited) Change-Id: I84539f555be498dff18caed1e3eea1e1aeb2143a Signed-off-by: Michael Stack <stack@apache.org> |
||
|---|---|---|
| .. | ||
| 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 apart
from the build. Run the generation whenever you make changes to the .orotos files
and then check in the produced java (The reasoning is that change is infrequent
so why pay the price of generating files anew on each build.
To generate java files from protos run:
$ mvn compile -Dcompile-protobuf
or
$ mvn compile -Pcompile-protobuf
After you've done the above, check it and then check in changes (or post a patch
on a JIRA with your definition file changes and the generated files). Be careful
to notice new files and files removed and do appropriate git rm/adds.