tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neale Upstone (JIRA)" <>
Subject [jira] [Commented] (MTOMCAT-60) Multiple-War-Deployment in configuration section.
Date Fri, 15 Jun 2012 13:33:44 GMT


Neale Upstone commented on MTOMCAT-60:

Looks good in that I get the correct context now (in fact I can deploy the same dependency
to different context paths):
[INFO] Deploy warfile: /snip/blah-SNAPSHOT.war to contextPath: /blah
[INFO] Deploy warfile: /snip/blah-SNAPSHOT.war to contextPath: /pathOfMyChoosing

However. There is a regression in 2.0-rc1 in that an EMPTY context.xml is created in /tmp,
which then blows up with a SaxParseException. That file should only be created if it has content.

> Multiple-War-Deployment in configuration section.
> -------------------------------------------------
>                 Key: MTOMCAT-60
>                 URL:
>             Project: Apache Tomcat Maven Plugin
>          Issue Type: Improvement
>            Reporter: Joerg Bellmann
>            Priority: Minor
>         Attachments: maven-tomcat-plugin.patch.txt, patch-for-tomcat6.patch
> 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:
> {code}
> [INFO] Scanning for projects...
> [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] It is highly recommended to fix these problems because they threaten the stability
of your build.
> [WARNING] For this reason, future Maven versions might no longer support building such
malformed projects.
> {code}
> Configuring the additional webapps in the configuration section like this for example
> {code}
> 			<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>
> {code}
> 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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message