Incompatible artifactId change so can have htrace 3.2 and htrace 4.0 on same CLASSPATH. Examples of where we need this are an hbase updated to use 4.0 APIs but using an HDFS that has the old APIs or, inside in htrace itself, the htrace-hbase module can't be updated to hbase 1.0.0 because hbase 1.0.0 is on htrace 3.2.
With a different artifactId and different package names, no possibility of NoClassDefFound.
- is required by
HTRACE-114 Fix compilation error of htrace-hbase against hbase-1.0.0