We could do that. "Hadoop-client" is a superset of hadoop-common + hadoop-mapreduce-client-core. However, as good hygiene, I would prefer to describe the exact direct dependencies. That would tend to keep your transitive dependencies slim and prevent dependency creep. The actual implication of using hadoop-client over the current is to pull in some additional hadoop jars (hdfs, mapreduce-client-app, mapreduce-client-common, mapreduce-client-jobclient, mapreduce-client-shuffle, yarn-client, and yarn-server-common). Obviously the current hadoop-lzo code base does not use them...