anchor.diff:            </filesets>
           </configuration>
         </plugin>
  -
  +---------
  +
  +So yeah, the GWT tools (compiler, Dev Mode, and the JUnit test
  +harness) generate a lot of junk in a lot of places. Errai also
  +generates junk, but it's a bit more polite and keeps it all under one
  +.errai directory.
  +
  +The one thing to keep in mind here is the commented line: if you
  +rename your GWT module (we'll talk about GWT modules in the next
  +section) you will also have to update this line to match. If the `mvn
  +clean` command fails to remove your generated GWT module directory,
  +you will run into the dreaded 'Module __yourmodule__ may need to be
  +(re)compiled' error.
  +
  +And now on to the resources plugin:
  +
  +---------
         <plugin>
           <groupId>org.apache.maven.plugins</groupId>
           <artifactId>maven-resources-plugin</artifactId>
  
positive.code:               <goal>copy-resources</goal>
              </goals>
              <configuration>
                <outputDirectory>${basedir}/target/classes</outputDirectory>
                <resources>
                  <resource>
                    <directory>target/generated-sources/annotations</directory>
                  </resource>
                </resources>
              </configuration>
            </execution>
          </executions>
        </plugin>
  
        <plugin>
          <groupId>org.jboss.as.plugins</groupId>
          <artifactId>jboss-as-maven-plugin</artifactId>
  
negative.code:                 <include>.errai/**</include>
                  <include>src/main/webapp/WEB-INF/deploy/**</include>
                  <include>src/main/webapp/WEB-INF/lib/**</include>
  
                  <!-- If you rename your GWT module, you MUST update this too -->
                  <include>src/main/webapp/UberFireTutorial/**</include>
  
                  <include>**/gwt-unitCache/**</include>
                  <include>**/*.JUnit/**</include>
                  <include>monitordb.*</include>
  