title: Publishing Gradle snapshots locally
body: <p>Here is my <code>dummy</code> project's <code>build.gradle</code> file:</p>
  
  <pre><code>apply plugin: 'groovy'
  
  repositories {
      mavenLocal()
      mavenCentral()
  }
  
  dependencies {
      compile 'org.codehaus.groovy:groovy-all:2.3.3'
      compile 'org.slf4j:jcl-over-slf4j:1.7.7'
  
      testCompile 'junit:junit:4.11'
      testCompile 'org.mockito:mockito-all:1.10.8'
  }
  
  task sourcesJar(type: Jar, dependsOn: classes) {
      classifier = 'sources'
      from sourceSets.main.allSource
  }
  
  artifacts {
      archives sourcesJar
  }
  
  task wrapper(type: Wrapper) {
      gradleVersion = '1.11'
  }
  </code></pre>
  
  <p>When I run <code>gradle clean build -Pversion=1.2.3</code>, this packages up all my code and creates a <code>build/libs/dummy-1.2.3.jar</code> for me.</p>
  
  <p>I would like to know the absolute <em>bare minimum</em> amount of Gradle code necessary so that I could publish my "dummy" JARs to my local Maven cache (<code>mavenLocal()</code>). Additionally, how does this work with versioning? I <em>could</em> always specify a concrete version for the dummy JAR, but when I'm publishing locally, it makes more sense (to me, at least) to publish <code>SNAPSHOT</code> versions. I <em>could</em> just run <code>gradle clean build -Pversion=0.1.SNAPSHOT</code>, but then my concern is whether or not other local projects would pick up the latest <code>SNAPSHOT</code> versions.</p>
  
  <p>So again:</p>
  
  <ol>
  <li>What's the bare minimum code to publish <code>dummy</code> locally?</li>
  <li>Any way, when publishing locally, to specify a <code>SNAPSHOT</code> version that other projects always pick up the latest copy of?</li>
  <li>What would other local projects need to use to pick up this <code>SNAPSHOT</code>? Something like <code>compile ':dummy:LATEST'</code>?</li>
  </ol>