title: Gradle: pros/cons adding dependencies
body: <p>What are some pros/cons adding dependencies in <code>build.gradle</code>, instead of adding them as dependent libraries?</p>
  <pre><code>dependencies {
      compile project(':library')
      ...
      compile 'com.stackoverflow.android:some-great-library:1.0'
      ...
  }
  </code></pre>
  <p>While working on Android projects, I've frequently come across with great libraries with the exact solution I've been looking for. However, as what I need is only a fraction of what those particular libraries have to offer, I'm worried if adding them as <code>Gradle dependencies</code> is an <em>overkill</em>.</p>
  <hr />
  <h3>Per @CommonsWare's comment, I have more specific questions.</h3>
  <p>Does adding dependencies:</p>
  <blockquote>
  <ol>
  <li><p>slow down compilation time at a noticeable rate?</p>
  </li>
  <li><p>increase the size of release-apk and debug-apk, as much as the size of the added dependency?</p>
  </li>
  </ol>
  </blockquote>