anchor.diff:      </resources>
   
       <plugins>
  +      <!-- see below in this guide -->
  +    </plugins>
  +
  +  </build>
  +---------
  +
  +The `<resources>` section adds `src/main/java` as a resource
  +directory, and reaffirms that `src/main/resources` is also a resource
  +directory. The purpose of adding `src/main/java` as a resource
  +directory is to ensure all the .java source files are included on the
  +build path. The GWT compiler requires this. The reason we add
  +`src/main/resources` redundantly is because the Maven integration in
  +IntelliJ IDEA does not retain this default resource directory when you
  +add a new one. Adding both provides maximum compatibility.
  +
  +Now, how do we teach Maven to perform the extra build steps that are
  +unique to an UberFire-based project? That's where the plugins come in.
  +
  +Note that all of the following `<plugin>` elements go inside the
  +`<plugins>` placeholder we defined in the previous step.
  +
  +First up, we'll define some settings for `maven-compiler-plugin`:
  +
  +---------
         <plugin>
           <groupId>org.apache.maven.plugins</groupId>
           <artifactId>maven-compiler-plugin</artifactId>
  
positive.code:           </execution>
          </executions>
        </plugin>
  
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-war-plugin</artifactId>
  
negative.code:           </dependency>
          </dependencies>
        </plugin>
  ---------
  
  The `source` and `target` options set the compiler for Java 1.6
  compliance. This is the version of the Java language that GWT 2.5
  supports.
  
  The dependency on `uberfire-workbench` is the recommended way of
  hinting Eclipse's Maven integration that this module contains Java
  Annotation Processors that should be executed whenever an incremental
  build is performed. More on this later (TODO: link to m2e setup).
  
  Next up, the all-important `gwt-maven-plugin`.
  
  ---------
        <plugin>
          <groupId>org.codehaus.mojo</groupId>
          <artifactId>gwt-maven-plugin</artifactId>
          <version>${maven.gwt.plugin.version}</version>
          <configuration>
  
            <noServer>true</noServer>
  
            <!-- Change to false if using client-side Bean Validation -->
            <strict>true</strict>
  
            <!-- If you can't use strict mode, diagnose mysterious
                 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 -->
            <extraJvmArgs>-Xmx1g -Xms756m -XX:MaxPermSize=256m -XX:CompileThreshold=1000</extraJvmArgs>
  
            <gwtSdkFirstInClasspath>true</gwtSdkFirstInClasspath>
  
          </configuration>
          <executions>
            <execution>
  