anchor.diff:  ---------
   
   Now, underneath the properties section, we'll import four Maven __BOM__
  -files. BOM (short for Bill Of Materials) is a Maven pattern that allows
  -frameworks to publish a comprehensive set of dependency versions that
  +files. BOM (short for Bill Of Materials) is a Maven pattern where
  +frameworks publish a comprehensive set of dependency versions that
   are known to work well with the framework. We'll import BOMs for
   UberFire, Errai, and the Java EE 6 APIs.
   
  
positive.code:           <!-- 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>
  
negative.code:           <filename>${project.artifactId}.${project.packaging}</filename>
          </configuration>
        </plugin>
  ---------
  
  The `jboss-as-maven-plugin` is a handy tool that lets you deploy and
  undeploy your project from JBoss AS 7, EAP 6, or WildFly 8. As long as
  one of those servers is running locally, you can deploy your app to it
  with the command `mvn jboss-as:deploy`.
  
  Phew! That's it for the `<plugins>` section. Just one more section to
  go, and you can skip it if nobody will even use Eclipse to develop
  your project.
  
  The `<pluginManagement>` section goes inside the `<build>` section
  (it's a sibling of <plugins>, not a child).
  
  ---------
      <pluginManagement>
        <plugins>
          <!--This plugin's configuration is used to store Eclipse m2e settings 
            only. It has no influence on the Maven build itself. -->
          <plugin>
            <groupId>org.eclipse.m2e</groupId>
  