I think you need to read up a bit on how slf4j works.
Libraries which use slf4j should only expose a dependency on the
slf4j-api. This is what hector (at least with some of my pom
tidy-up... not sure about the exact version) should now be doing.
The net result is that you, as a consumer, do not have a slf4j
implementation on your classpath... this is good as the library
producer does not know what logging framework you want to use.
To solve this issue you need to add a dependency to one of the slf4j
implementations... "which one?" I hear you ask... that depends on what
logging provider you are using. The two most common ones are the
log4j and the java utils providers (slf4j-log4j and slf4j-jdk14
respectively)... "which version?" you now chime in... well it needs to
be at least the version used by hector, and if you are using a newer
version you will have to add a dependency to your project on the
corresponding version of slf4j-api in order to ensure that the
transitive resolution picks the same version of the api as the impl.
-Stephen
Great answer!
Asil