title: Maven SNAPSHOT jar file names not consistent using Maven Assembly in MANIFEST file
body: <p>Here is the scenario:</p>
  
  <p>Two Maven 3 project builds.</p>
  
  <p>Build 1 has snapshot jars that get deployed to Nexus.</p>
  
  <p>Build 2 has dependencies on the snapshots, referenced like <em>1.0.0-SNAPSHOT</em>, that gets packaged up and zipped up using the <code>mvn clean package assembly:single</code> command.</p>
  
  <p>The issue that we run into:
  Occasionally when the assembly is being created, the MANIFEST file for the jar will sometimes say <em>some.jar.1.0.0-SNAPSHOT</em> and sometimes it will say <em>some.jar.1.0.0-datetime stamp</em>, thus causing class not defined errors.</p>
  
  <p>Is there a way to prevent this naming issue in the manifest file?</p>
  
  <p>--edit--</p>
  
  <p>Further research has discovered the following:</p>
  
  <blockquote>
    <p>"If the snapshot was resolved from a repo then it will be timestamped,
    if it came from the reactor or local repo, then it will be -SNAPSHOT.
    The plugin calls into the maven resolution logic so this is core maven
    behavior. "</p>
  </blockquote>
  
  <p>This is the exact issue that is being run into.  The 2nd build manifest file always has an entry of <em>./lib/Framework-1.0.0-SNAPSHOT.jar</em> where as the actual jar file name changes between <em>./lib/Framework-1.0.0-SNAPSHOT.jar</em> and <em>./lib/Framework-1.0.0-timestamp.jar</em> based on the quote above.</p>