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

WAR deployed as "" or "/" under Tomcat 7 have their war copied over, but since the ROOT folder is not deleted by undeploy, the WAR is not expanded

Description

Undeploy never work. Also, it seems the plug-ins doesn't understand well that war file deployed in root will be mapped by Tomcat to ROOT.war because sometime it is very confused.

Maybe the undeploy doesn't work because after calling undeploy the script leave. I mean it seems undeploy is asynchronous so that if the server do not stay UP for a while after undeploy there is no hope it's going to work. This is unmanageable in a scripted environment. Why you don't just delete the uncompressed folder directly?

So some behavior are:

  • complain cannot find ".war" to be deleted

  • delete the war but do not delete the folder ROOT or what is inside

  • deploy the war but do not update what is inside folder ROOT.

It so buggy that I feel I'm the only one on the planet using Tomcat! No kidding.

Configuration like the following doesn't work well at all:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 <groupId>org.codehaus.cargo</groupId> <artifactId>cargo-maven2-plugin</artifactId> <version>1.1.4</version> <configuration> <container> <containerId>tomcat7x</containerId> <home>C:/Program Files/Apache Software Foundation/Tomcat 7.0_Tomcat7FunctionalTest</home> </container> <configuration> <!-- Configuration to use with the container --> <home>C:/Program Files/Apache Software Foundation/Tomcat 7.0_Tomcat7FunctionalTest</home> <type>existing</type> <properties> <cargo.servlet.port>${web.server.port}</cargo.servlet.port> <cargo.rmi.port>85</cargo.rmi.port> <cargo.tomcat.ajp.port>89</cargo.tomcat.ajp.port> <cargo.jvmargs>-XX:PermSize=512m -XX:MaxPermSize=512m -Xmx1524m -Xms512m</cargo.jvmargs> </properties> </configuration>

Status

Assignee

Unassigned

Reporter

Sebastien Tardif

Components

Fix versions

Affects versions

1.1.4

Priority

Major