a45651c2cf
* corrects license/notice for source distribution * adds inception year to correct copyright in generated NOTICE files for jars * updates project names in poms to use "Apache HBase" instead of "HBase" so jar NOTICE files will be correct * uses append-resources to include supplemental info on jars with 3rd party works in source * adds an hbase specific resource bundle for jars that include 3rd party works for binaries ** uses supplemental-model to fill in license gaps ** uses the above and a shade plugin transformation to build proper files for shaded jars. ** uses the above and the assembly plugin to build the proper files for bin assembly * adds a NOTICE item for things copied out of Hadoop (TODO legal-discuss) Conflicts: NOTICE.txt hbase-checkstyle/pom.xml hbase-resource-bundle/pom.xml hbase-server/pom.xml hbase-thrift/pom.xml pom.xml
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: https://github.com/google/protobuf/releases/tag/v2.5.0). 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).