Note that there are some explanatory texts on larger screens.

plurals
  1. POMaven artifact version number in jar file
    primarykey
    data
    text
    <p>I am using Maven 3 for build xxx-common module</p> <p>After building my application i get my jar file as xxx-common-0.0.1.jar</p> <p>this is getting deployed into my artifactory as </p> <p><a href="http://localhost:8800/artifactory/core-release/com/xxx/xxx-common/0.0.1/xxx-common-0.0.1.jar" rel="nofollow">http://localhost:8800/artifactory/core-release/com/xxx/xxx-common/0.0.1/xxx-common-0.0.1.jar</a></p> <p>That deployment is good, </p> <p>Here, how can I eliminate version number getting appended " <strong>xxx-common-0.0.1.jar</strong> " and need it just as " <strong>xxx-common.jar</strong> "</p> <p>Kindly help out to overcome this problem guys...</p> <hr> <p>Sorry it didn't worked out </p> <p>Below is what i gave....</p> <pre><code>&lt;plugins&gt; &lt;plugin&gt; &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-jar-plugin&lt;/artifactId&gt; &lt;version&gt;2.3.2&lt;/version&gt; &lt;configuration&gt; &lt;finalName&gt;${project.artifactId}&lt;/finalName&gt; &lt;/configuration&gt; &lt;/plugin&gt; &lt;plugin&gt; &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-compiler-plugin&lt;/artifactId&gt; &lt;version&gt;2.1&lt;/version&gt; &lt;configuration&gt; &lt;source&gt;1.6&lt;/source&gt; &lt;target&gt;1.6&lt;/target&gt; &lt;/configuration&gt; &lt;/plugin&gt; &lt;/plugins&gt; </code></pre> <p>executed using </p> <p>mvn package</p> <p>and </p> <p>Installing /home/xxx/build-deploy-tools/.jenkins/jobs/workspace/xxx-common/target/xxx-common.jar to /home/xxx/.m2/repository/com/xxx/xxx-common/0.0.1/xxx-common-0.0.1.jar</p> <p>Still it pushes as xxx-common-0.0.1.jar</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload