anchor.diff:  Moving on, we set `runTarget` to the local URL where your webapp will
   be served by the JBoss EAP or WildFly server on your workstation.
   
  -The `extraJvmArgs` setting increases the memory limits for the Dev
  -Mode JVM, and asks its JIT compiler to be more aggressive in
  -generating native code. We've done some experimenting and found a
  -compile threshold of 1000 allows Dev Mode to start up a little faster.
  +The `extraJvmArgs` setting passes some information to Errai's
  +`JBossLauncher`, increases the memory limits for the Dev Mode JVM, and
  +asks its JIT compiler to be more aggressive in generating native
  +code. We've done some experimenting and found a compile threshold of
  +1000 allows Dev Mode to start up a little faster.
   
   Next up, we configure `maven-war-plugin`, which produces the WAR file
   during the build's _package_ phase:
  
positive.code: 
  This is a lot to digest. Let's take it one step at a time.
  
  First, we configure `noServer` because we'll be doing our Dev Mode
  testing against a real JBoss EAP or WildFly instance. We don't want
  Dev Mode to start its embedded Jetty server.
  
  Next, we enable GWT's strict mode. This causes the build to fail with
  a helpful error message when you use Java APIs that aren't available
  
negative.code:         <version>${maven.gwt.plugin.version}</version>
          <configuration>
  
            <server>org.jboss.errai.cdi.server.gwt.JBossLauncher</server>
  
            <!-- Change to false if using client-side Bean Validation -->
            <strict>true</strict>
  