This is the minimal support the plugin should offer in order to allow for simple iterative development of a web app.

We are re-using start/deploy/shutdown goals and integrate them with the package/provision goals.

A typical sequence of steps would look like:

• mvn package ⇒ deployment deployed to trimmed WildFly server in target/server
• mvn wildfly:start ⇒ server started
• Developper makes change
• mvn wildfly:deploy ⇒ deployment re-deployed 
• mvn wildfly:shutdown

A user should be able to provision a server in any location, not only under target directory.

Provisioning would not occur if a server already exists. The option force-provisioning would force a delete and re-provisioning of the server.