Merge pull request #1303 from ctron/feature/enh_maven_plugin_1

Allow to externally provide 'daemon' parameter

jetty-documentation/src/main/asciidoc/development/maven/jetty-maven-plugin.adoc

@@ -487,7 +487,7 @@ Here's how to set it:
 ==== jetty:run-exploded
 
 The run-exploded goal first assembles your webapp into an exploded WAR file and then deploys it to Jetty.
-If you set a non-zero `scanInterval`, Jetty watches your `pom.xml,`WEB-INF/lib`, `WEB-INF/` and `WEB-INF/web.xml` for changes and redeploys when necessary.
+If you set a non-zero `scanInterval`, Jetty watches your `pom.xml`, `WEB-INF/lib`, `WEB-INF/` and `WEB-INF/web.xml` for changes and redeploys when necessary.
 
 [[configuring-exploded-war]]
 ===== Configuration
@@ -527,9 +527,10 @@ Unlike `run-war`, the phase in which this plugin executes is not bound to the "p
 war::
 The location of the WAR file. This defaults to `${project.build.directory}/${project.build.finalName}`, but you can override the default by setting this parameter.
 daemon::
-If true, this plugin will start Jetty but let the build continue.
+If true (the default), this plugin will start Jetty but let the build continue.
 This is useful if you want to start jetty as an execution binding in a particular phase and then stop it in another.
-Alternatively, you can set this parameter to false, in which case Jetty will block and you will need to use a ctrl-c to stop it.
+Alternatively, you can set this parameter to false, in which case Jetty will block and you will need to use a ctrl-c to stop it. The parameter can also be set
+using the property `jetty.daemon`.
 
 Here's the configuration:
 

jetty-maven-plugin/src/main/java/org/eclipse/jetty/maven/plugin/JettyDeployWar.java

@@ -53,7 +53,7 @@ public class JettyDeployWar extends JettyRunWarMojo
      * cntrl-c to stop it.
      * 
      * 
-     * @parameter  default-value="true"
+     * @parameter property="jetty.daemon" default-value="true"
      */
     protected boolean daemon = true;