 <p>I found the solution: Because I was using a auto generated pom.xml, I added the <code>maven-s3-wagon</code> extension to publish the library to a Maven repo on a AWS S3 server. So, the <code>pom.xml</code> file had other plugins for Maven. I think that <code>mvn</code> was calling both processes: the <em>regular Maven</em> deployment and the <em>Maven S3 Wagon</em>, and that would be the reason why the deployment process was doing an "extra step" and generating two names: artifact-id-xxxx.<strong>142230-1</strong> and artifact-id-xxxx.<strong>142243-2</strong></p> <p>I removed all the plugins into <code>&lt;build&gt;</code> section and leave only the <code>maven-s3-wagon</code> extension. It worked like a charm.</p> <pre><code>&lt;build&gt; &lt;extensions&gt; &lt;extension&gt; &lt;groupId&gt;org.kuali.maven.wagons&lt;/groupId&gt; &lt;artifactId&gt;maven-s3-wagon&lt;/artifactId&gt; &lt;version&gt;1.2.1&lt;/version&gt; &lt;/extension&gt; &lt;/extensions&gt; &lt;/build&gt; </code></pre>