Maven : How to avoid version appended to a war file in Maven?

Question

I am using Maven as the build file , this is my below settings for the war file name to be generated

I am using Maven version 2.2.1

     <artifactId>TataWeb</artifactId>
<packaging>war</packaging>
<version>1.0</version>

So its actually generating a war file with this name TataWeb-1.0

But i want the war file name to be only TataWeb .

Please let me know how can i avoid the version appeneded to the war file name ??

Thank you .

score 28 · Accepted Answer · answered May 11 '12 at 09:10

28

Just add this to your pom.xml:

<build>
    <finalName>TataWeb</finalName>
</build>

answered May 11 '12 at 09:10

Tomasz Nurkiewicz

I have 6 pom.xml files , one is parent one , where exactly i need to add this ?? – user1253847 May 11 '12 at 09:18
@user1253847: in the `pom.xml` responsible for generating WAR file, i.e. the one with `war`. – Tomasz Nurkiewicz May 11 '12 at 09:30
Ya i did that , but that did not work , still its generating with Tataweb-1.0.war , i have added the pom.xml file , please see . – user1253847 May 11 '12 at 09:41
@user1253847: are you sure you are building your application with `tata` profile? Because the `finalName` is defined only there. – Tomasz Nurkiewicz May 11 '12 at 09:49
2

The finalName will only prevent adding the information in the target folder but will not prevent the information added during deployment. – khmarbaise May 11 '12 at 12:29

score 9 · Answer 2 · answered Nov 02 '15 at 04:29

9

You should use your artifactid, rather than hard-coding the file name.

<build>
  <finalName>${project.artifactId}</finalName>
</build>

answered Nov 02 '15 at 04:29

J. M. Becker

score -1 · Answer 3 · answered May 11 '12 at 14:29

-1

well, its not the Maven Way. Maven does have a version attribute.. use it.

answered May 11 '12 at 14:29

rk2010

1

Even though it is not the maven way, there are some cases when someone has to do this. – Damien May 03 '13 at 20:38

score -2 · Answer 4 · answered Mar 12 '14 at 15:18

-2

You can avoid the version appeneded to the war file name by doing a "clean compile package" instead of "clean install".

answered Mar 12 '14 at 15:18

Nirmalya

Because, this will not install it to the local maven repo. So, file name changing angle, it is similar to build/finalName solution given above IMO. – ironwood Apr 21 '15 at 09:04

4 Answers4