My approach (with maven) is the following: 1. Co-processors package is built as separate artifact and they are tested in context of another module as part of integration testing. 2. Module is built with co-processor package placed with dependency plugin. It's location is passed to test through system property and failsafe plugin. 3. Test setups HBase mini-cluster. Here is good article: http://blog.cloudera.com/blog/2013/09/how-to-test-hbase-applications-using-popular-tools/ 4. Of course I need to place co-processors to HDFS first and then create tables that use them as region observer. 5. For master co-processor check appropriate tests in HBase itself. They extend root co-processor to test it. I have implemented the same approach.
Good luck to you! Roman. On 29 January 2014 09:19, Joshi, Rekha <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext