Lets. We have a new package for htrace-4.0.0 but the groupId and artifactIds are the same as for htrace 3.2 so we've run into a few interesting issues trying to make use of htrace-4.0.0 when a dependent depends on htrace-3.2.0 (see https://issues.apache.org/jira/browse/HBASE-14451 for an illustration). Maven won't let you bundle two versions of same artifact (see https://issues.apache.org/jira/browse/HTRACE-114 for my failed attempt at convincing maven to do otherwise trying to fix another clash of the versions).
I agree we should put up a 4.0.1 with a different artifactId. St.Ack On Fri, Sep 18, 2015 at 5:54 PM, Colin P. McCabe <[email protected]> wrote: > Hi all, > > We found some blocker issues with integrating the 4.0 release with > Hadoop and HBase. There is a really chatty log message in Tracer.java > which causes problems for people running commands like "hadoop fs > -ls", who generally don't want to see output on the command-line. > Also, since we used the same artifactId as HTrace 3, we have been > having some dependency issues with Maven. > > We'd like to do a 4.0.1 release which fixes these problems and lets us > do the Hadoop / HBase integration as planned. The only other changes > in this release will be a few build cleanups to improve the stability > and clarity of the build. > > best, > Colin >
