For sure. I'm new to sbt and have a few questions about plugins and how scalding likes to use them. So, the travis build is currently failing because of conflicting dependencies. In maven, I would use `mvn dependency:tree` to figure out what the conflict is and where those dependencies are getting pulled in from. Is there a way to do this with vanilla sbt? I've found a plugin (https://github.com/jrudolph/sbt-dependency-graph) that will make nice graphs of a project's dependencies, but it requires modifying the build.sbt file - which seems like overkill. Second, sillier, sbt question- I have to use pgp to publish this artifact locally (which I want to do for manual testing) but this seems silly. Supposedly this was fixed in sbt-pgp 0.8 (see https://github.com/sbt/sbt-pgp/issues/12) any objection to bumping the version to 0.8? Or is there a way around the publish-local pgp business that I don't know about?