title: Android Libraries: maven vs maven-publish gradle project
body: <p>I'm building a large multi-module Android library, and need to publish the library to an internal company Artifactory.</p>
  
  <p><strong>Should I use the old <a href="https://docs.gradle.org/current/userguide/maven_plugin.html" rel="noreferrer"><code>maven</code></a> plugin, or the new <a href="https://docs.gradle.org/current/userguide/publishing_maven.html" rel="noreferrer"><code>maven-publish</code></a> plugin?</strong></p>
  
  <p>Note: The above two official plugins don't fully support Android, so there are two community ports.</p>
  
  <ul>
  <li><a href="https://github.com/dcendents/android-maven-gradle-plugin" rel="noreferrer">unofficial <code>maven</code> plugin</a></li>
  <li><a href="https://github.com/wupdigital/android-maven-publish" rel="noreferrer">unofficial <code>maven-publish</code> plugin</a></li>
  </ul>
  
  <p>Also interesting - the Android Tools team <a href="http://tools.android.com/tech-docs/new-build-system/gradle-experimental" rel="noreferrer">deprecated the experimental gradle plugin</a> that was based around the SoftwareComponent model - which is what the <code>maven-publish</code> plugin uses. Is <code>maven-publish</code> deprecated too then?</p>