to follow up with an example,

JIRA on updating dependencies and tuning the POMs
 here's a JIRA on dropping ZK from the hadoop-client POM

And there's an mr-client POM where we've been slowly cutting down on what
it pulls in

This shows that
1. we can given maven/ivy projects what they need -and no more- through
POM-only projects.
2. its an ongoing project to keep those dependencies cut down.
3. there's always the risk that you drop too much and some project
discovers that while their code builds, it doesn't run any more.

NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.

NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB