We're updating the issue view to help you get more done. 

Deploying a WAR into <context>ROOT</context> results in two apps being deployed

Description

I got this to work by using:

<deployable>
<properties>
<context>ROOT</context>
</properties>
</deployable>

(full configuration below)

I'm using the cargo-maven2-plugin 0.3.1. Unfortunately, it seems to
have a bug in that it deploys the WAR twice - once at / and a second
time at /ROOT. Obviously, its not that big of a deal, but if I use
<context>anything</context>, it only deploys it once.

Thanks,

Matt

<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<version>0.3.1</version>
<configuration>
<wait>${cargo.wait}</wait>
<container>
<containerId>${cargo.container}</containerId>
<!--home>${cargo.container.home}</home-->
<zipUrlInstaller>
<url>${cargo.container.url}</url>
<installDir>${installDir}</installDir>
</zipUrlInstaller>
</container>
<configuration>
<home>${project.build.directory}/${cargo.container}/container</home>
<properties>
<cargo.hostname>${cargo.host}</cargo.hostname>
<cargo.servlet.port>${cargo.port}</cargo.servlet.port>
</properties>
<deployables>
<deployable>
<properties>
<context>ROOT</context>
</properties>
</deployable>
</deployables>
</configuration>
</configuration>
<executions>
<execution>
<id>start-container</id>
<phase>pre-integration-test</phase>
<goals>
<goal>start</goal>
</goals>
</execution>
<execution>
<id>stop-container</id>
<phase>post-integration-test</phase>
<goals>
<goal>stop</goal>
</goals>
</execution>
</executions>
</plugin>

Status

Assignee

Unassigned

Reporter

Matt Raible

Components

Fix versions

Affects versions

0.3.1-maven2

Priority

Major