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: The ErraiServlet manages the communication bus that allows
  two-way-push communication between the client and the server.
  
  == Set up UberFire security
  
  === Choose how users and roles are defined
  
negative.code: 
  This is a lot to digest. Let's take it one step at a time.
  
  First, we configure GWT to use Errai's `JBossLauncher`, which manages
  deployment of your webapp to a real JBoss EAP or WildFly instance. We
  don't want Dev Mode to start its embedded Jetty 6 server, because that
  makes it difficult to set up CDI, JPA, and other features that work
  well with UberFire and Errai.
  
  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
  