the pom.xml excerpt below shows the structure of the project that leads to ever an ever growing war file:
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
...
</parent>
<artifactId>...</artifactId>
<packaging>war</packaging>
<name>...</name>
<description>...</description>
<dependencies>
<!-- ...-->
<dependency>
<artifactId>...</artifactId>
<groupId>${project.groupId}</groupId>
<version>${project.version}</version>
</dependency>
</dependencies>
<build>
<plugins>
<!-- tomcat deployment -->
<plugin>
<groupId>org.apache.tomcat.maven</groupId>
<artifactId>tomcat7-maven-plugin</artifactId>
<version>2.2</version>
<configuration>
<url>...</url>
<server>...</server>
<path>...</path>
<webXml>src/main/webapp/WEB-INF/web.xml</webXml>
</configuration>
</plugin>
</plugins>
</build>
</project>
the war contains as many jar files as the local maven repository has timestamped snapshot versions.
How can this be reduced to just the current version?
I have found a workaround in:
to use another maven plugin to remove superfluous timestamped snapshot version jars
And i have filed a bug report at https://issues.apache.org/jira/browse/MTOMCAT-268