hbase/hbase-protocol
mbertozzi 788b285e11 HBASE-8332 Add truncate as HMaster method
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1593439 13f79535-47bb-0310-9956-ffa450edef68
2014-05-08 22:25:01 +00:00
..
src/main HBASE-8332 Add truncate as HMaster method 2014-05-08 22:25:01 +00:00
README.txt HBASE-10020 Add maven compile-protobuf profile 2013-11-27 23:57:23 +00:00
pom.xml HBASE-10806 Two protos missing in hbase-protocol/pom.xml (Liu Shaohui) 2014-03-21 18:00:27 +00:00

README.txt

These are the protobuf definition files used by hbase. The produced java
classes are generated into src/main/java/org/apache/hadoop/hbase/protobuf/generated
and then checked in.  The reasoning is that they change infrequently.

To regenerate the classes after making definition file changes, ensure first that
the protobuf protoc tool is in your $PATH (You may need to download it and build
it first; its part of the protobuf package obtainable from here: 
http://code.google.com/p/protobuf/downloads/list).

HBase uses hadoop-maven-plugins:protoc goal to invoke the protoc command. You can 
compile the protoc definitions by invoking maven with profile compile-protobuf or 
passing in compile-protobuf property. 

mvn compile -Dcompile-protobuf
or
mvn compile -Pcompile-protobuf

You may also want to define protoc.path for the protoc binary

mvn compile -Dcompile-protobuf -Dprotoc.path=/opt/local/bin/protoc

If you have added a new proto file, you should add it to the pom.xml file first.
Other modules also support the maven profile.

After you've done the above, check it in and then check it in (or post a patch
on a JIRA with your definition file changes and the generated files).