anchor.diff:                 rebind errors by setting this to DEBUG -->
             <logLevel>INFO</logLevel>
   
  -          <runTarget>http://localhost:8080/${project.artifactId}/</runTarget>
  -
  -          <!-- do not insert line breaks in this string; it breaks Windows compatibility -->
  +          <runTarget>${project.artifactId}</runTarget>
  +
  +          <!-- do not insert line breaks in this string; it breaks
  +          Windows compatibility -->
             <extraJvmArgs>-Xmx1g -Xms756m -XX:MaxPermSize=256m -XX:CompileThreshold=1000 -Derrai.jboss.home=${errai.jboss.home} -Derrai.jboss.javaopts=-XX:MaxPermSize=256m -Derrai.dev.context=${project.artifactId} -Derrai.jboss.javaagent.path=${settings.localRepository}/org/jboss/errai/errai-client-local-class-hider/${errai.devmode.version}/errai-client-local-class-hider-${errai.devmode.version}.jar</extraJvmArgs>
   
           </configuration>
  
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
  