[MTOMCAT-60] Multiple-War-Deployment in configuration section.

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.0
• Assignee: Olivier Lamy
• Reporter: Joerg Bellmann
• Created: 10/Aug/10 02:07
• Updated: 19/Jun/12 15:49
• Resolved: 19/Jun/12 15:31

Description

When a user want to deploy multiple webapps with the plugin it uses all project-war-dependencies with scope 'tomcat'. Maven 3 shows the following message at project-processing:

[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for de.jbellmann.failsafe:de.jbellmann.failsafe.web:war:0.0.1-SNAPSHOT
[WARNING] 'dependencies.dependency.scope' for org.springframework.samples:mvc-showcase:war must be one of [provided, compile, runtime, test, system] but is 'tomcat'. @ 
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.

Configuring the additional webapps in the configuration section like this for example :

			<plugin>
				<groupId>org.codehaus.mojo</groupId>
				<artifactId>tomcat-maven-plugin</artifactId>
				<version>1.1-SNAPSHOT</version>
				<executions>
					<execution>
						<id>start-tomcat-integration-tests</id>
						<goals>
							<goal>run</goal>
						</goals>
						<phase>pre-integration-test</phase>
						<configuration>
							<fork>true</fork>
							<addContextWarDependencies>true</addContextWarDependencies>
								<additionalWebapps>
									<webapp>
										<groupId>org.springframework.samples</groupId>
										<artifactId>mvc-showcase</artifactId>
										<version>1.0.0-BUILD-SNAPSHOT</version>
										<contextPath>/mvc-showcase2</contextPath>
									</webapp>
								</additionalWebapps>
						</configuration>
					</execution>
				</executions>
			</plugin>

avoids the warnings and makes maven 3 happy.

As a plus you can configure an contextPath different from the artifactId.

This solution was inspired by the 'maven-dependency-plugin' and uses some code-snippets from it.

Jörg Bellmann