[jboss-jira] [JBoss JIRA] (AS7-4741) Add a mode to the jboss-as maven plugin where undeploying an application that isn't deployed doesn't fail

[Pete Muir (JIRA)]

Pete Muir created AS7-4741:
------------------------------

             Summary: Add a mode to the jboss-as maven plugin where undeploying an application that isn't deployed doesn't fail
                 Key: AS7-4741
                 URL: https://issues.jboss.org/browse/AS7-4741
             Project: Application Server 7
          Issue Type: Feature Request
            Reporter: Pete Muir
            Assignee: James Perkins
             Fix For: 7.1.1.Final


Currently if I try to run

{code}
mvn jboss-as:undeploy
{code}

on a maven project which I haven't actually deployed to the application server (or have previously undeployed), the jboss-as maven plugin will give an error and cause maven to exit.

Consider a project like the quickstarts, where we have many deployable artifacts, of which the user may deploy a few. They then wish to undeploy any quickstarts, but currently have no easy way to do it, other than going to each quickstart they deployed and typing mvn jboss-as:undeploy (as doing a mvn jboss-as:undeploy at the root of the quickstart project will try to undeploy all of them, including those not yet deployed, and hence fail).

I think this is going to apply to development of any moderately complex project, where there is more than one deployable.
artifact.

I would propose that undeploying a non-existent project shouldn't be an error at all, but a warning, and that we should simply log this. We already have the force (true by default) flag, which could be extended to cover undeployment. If the user set force=false, then the error could occur.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira