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

Add the ability ignore failures when undeploy fails (for example, if the application is not deployed)


The deployment against a JBoass AS 7 is very restrictive.
One need to know the exact state of the server.

Is the application deployed or not?

1 2 It is not allowed to undeploy a not existent application. The resulting error is: [ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.2.1:deployer-undeploy (undeploy-project) on project XXX: Execution undeploy-project of goal org.codehaus.cargo:cargo-maven2-plugin:1.2.1:deployer-undeploy failed: Cannot undeploy deployable org.codehaus.cargo.container.jboss.deployable.JBossWAR[YYY.war]: Deployment action UNDEPLOY failed: "JBAS014807: Management resource '[(\"deployment\" => \"YYY.war\")]' not found" -> [Help 1]

With other application servers I could not recognize this behavior!

The original JBoss deployment plugin "jboss-as-maven-plugin" has the same strange behavior. But at least it gaves the option to deploy over an existing application via the use of "force".

In our usecase we want to undeploy the application before every new deployment - if it does exist. Of course this is not possible initial. But a Tomcat instance ignores that. JBoss throws an exception.

It would be nice, if cargo could catch this annoying exception.

And other option could be to support to "force" a deployment. JBoss supports to force a deployment. So it re-deploys, if the application does exist. I do not realy like the last solution, but it es better than nothing.

Thanks in advance for your reply!



Savas Ali Tokmen


Stephan Lau


Fix versions

Affects versions