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

A deployment failure should produce an error rather than an info

Description

If the cargo maven plugin is used to deploy an application for integration test (ex. into a glassfish container) and the deployment fails the plugin just produces an info like this:

1 2 3 4 [INFO] [talledLocalContainer] Deprecated syntax, instead use: [INFO] [talledLocalContainer] asadmin --interactive=false --port 4849 --user admin -passwordfile /opt/glassfishv3/.hudson/jobs/XAM Test.Setup.Application/workspace/target/cargo/configurations/glassfish3x/password.properties deploy [options] ... [WARNING] [talledLocalContainer] remote failure: Error occurred during deployment: Application with name de.rwth.swc.xam.tests.ear-0.0.1-SNAPSHOT is already registered. Either specify that redeployment must be forced, or redeploy the application. Or if this is a new deployment, pick a different name. Please see server.log for more details. [INFO] [talledLocalContainer] Command deploy failed.

The problem is, that this results in the build being sucessfull and therefore triggering other builds who may rely on successful deployment.

Also see: http://stackoverflow.com/questions/7160797/

Status

Assignee

Savas Ali Tokmen

Reporter

Matthias Vianden

Components

Fix versions

Affects versions

1.1.2

Priority

Major