anchor.diff:          <artifactId>maven-war-plugin</artifactId>
           <version>${maven.war.plugin.version}</version>
           <configuration>
  -          <failOnMissingWebXml>false</failOnMissingWebXml>
             <warName>${project.artifactId}</warName>
   
  -          <!-- Exclude GWT client local classes from the deployment,
  -	  lest 
  +          <!-- Exclude GWT client local classes from the deployment, lest 
               classpath scanners such as Hibernate and Weld get confused
  -	  when the webapp 
  -            is bootstrapping. -->
  -          <packagingExcludes>**/javax/**/*.*,**/client/**/*.class</packagingExcludes>
  +            when the webapp is bootstrapping. -->
  +          <packagingExcludes>**/client/**/*.class</packagingExcludes>
           </configuration>
         </plugin>
  -
  +---------
  +
  +The first configuration tweak changes the name of the generated .war
  +file to just __projectname__.war rather than the default
  +__projectname__-__version__.war. We find this more convenient to work
  +with, because the deployment URL remains stable that way. If you
  +prefer keeping the version number in the .war file name, feel free to
  +omit the `<warName>` setting.
  +
  +The `<packagingExcludes>` setting is vital, though: this keeps the
  +client-side-only classes off the web server. Anything that scans your
  +webapp for annotated classes or classes of a certain type (such as
  +Hibernate and Weld) tends to trip over classes that refer to GWT types
  +that only make sense in the client environment, such as Widgets and
  +JavaScript Native Methods. We'll get to these topics later, but for
  +now, just be sure to exclude your client-only classes from the .war
  +file.
  +
  +The `<packagingExcludes>` setting accepts a comma-separated list of
  +patterns, so if you need to exclude more stuff later on, you can.
  +
  +Now on to the clean configuration:
  +
  +---------
         <plugin>
           <groupId>org.apache.maven.plugins</groupId>
           <artifactId>maven-clean-plugin</artifactId>
  
positive.code:                 <include>.errai/**</include>
                  <include>src/main/webapp/WEB-INF/deploy/**</include>
                  <include>src/main/webapp/WEB-INF/lib/**</include>
                  <include>src/main/webapp/App/**</include>
                  <include>**/gwt-unitCache/**</include>
                  <include>**/*.JUnit/**</include>
                  <include>monitordb.*</include>
  
negative.code: 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 package phase of the build:
  
  ---------
        <plugin>
  