Ah yes, I did not think of that. Another option would be to move HBaseTestingUtility to hbase-core, but then hbase-core would need to be dependent on hadoop-(hdfs|mapred|core)-test, which is not ideal either. So it seems it is best to leave things as-is.
Thanks, Bruno. On Tue, Mar 2, 2010 at 9:49 PM, Dan Washusen <d...@reactive.org> wrote: > That would make it a little easier for external projects but how do you see > it working for hbase-core? If there was a separate module called hbase-test > it would need to have a dependency on hbase-core but hbase-core would need > to depend on hbase-test so it could run it's tests... > > Cheers, > Dan > > On 3 March 2010 03:20, Bruno Dumon <br...@outerthought.org> wrote: > >> Hi, >> >> I would like to use HBaseTestingUtility in my own testcases, in a >> Maven-based project. >> >> I can introduce it in my project via: >> >> <dependency> >> <groupId>org.apache.hbase</groupId> >> <artifactId>hbase-core</artifactId> >> <classifier>tests</classifier> >> </dependency> >> >> but this will not include the test-scoped dependencies of hbase-core >> (such as mapred-test, hdfs-test), so I have to add these manually to >> my project. >> >> This could be solved by putting HBaseTestUtility in its own project >> (hbase-test), with compile rather than test dependencies on things >> like hdfs-test. >> >> WDYT? >> -- Bruno Dumon Outerthought http://outerthought.org/
