title: How to ask maven to create maven-metadata.xml and not maven-metadata-local.xml?
body: <p>For some reasons (not the concern of this post) amazon S3 is not a perfect host for maven repository. so i am building my maven application in a local machine and at some points in time (like every two days or so) i copy the whole hierarchy to amazon S3 with <code>aws s3 cp</code> command. say i copy the com folder which is like :</p>
  
  <pre><code>com
  -raysis
  --rayProduct
  ---1.0-SNAPSHOT
  ----rayray.jar
  </code></pre>
  
  <p>the problem is the metadata file that has been created is <strong>maven-metadata-local.xml</strong> (since i have built it locally it seems reasonable) but when i upload it to S3 and trying to get it with maven, it complains that there is no <strong>maven-metadata.xml</strong>. so how can i force (or ask gracefully) maven to create maven-metadata.xml instead/along-side of maven-metadata-local.xml?
  since there is no location specific data inside  maven metadata, it seems not to be problem prone move. </p>
  
  <p>Note:
  i am trying to load the dependency from S3 with following dependency( i have added the repository too):</p>
  
  <pre><code>&lt;dependency&gt;
      &lt;groupId&gt;com.raysis&lt;/groupId&gt;
      &lt;artifactId&gt;sense-lib&lt;/artifactId&gt;
      &lt;version&gt;1.0-SNAPSHOT&lt;/version&gt;
  &lt;/dependency&gt;
  </code></pre>