anchor.diff:  CDI Bean that should be instantiated when the page is loaded into the
   browser. You can name an entry point class anything you like. You can
   create as many `@EntryPoint` classes as you want, but you can't
  -specify what order they will be instantiated in. It's unusual to have
  -more than one.
  -
  -The `start()` method is a CDI observer method. The UberFire Workbench
  +specify what order they will be instantiated in. Usually, you'll just
  +have one.
  +
  +The `init()` method is a CDI observer method. The UberFire Workbench
   framework fires an `ApplicationReadyEvent` when the framework has
   finished initializing.
   
  
positive.code: 
  [source,java]
  ---------
  @EntryPoint
  public class ClientEntryPoint {
    private void start(@Observes final ApplicationReadyEvent event) {
    }
  }
  ---------
  
  
negative.code:   </build>
  ---------
  
  The `<resources>` section adds `src/main/java` and
  `target/generated-sources/annotations` as resource directories, 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 classpath. The
  GWT compiler requires this. Similarly, UberFire has an annotation
  processor that outputs Java source files under
  `target/generated-sources/annotations`, and we need to ensure these
  source files are on the classpath too.
  
  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 it explicitly
  provides maximum compatibility.
  
  Now, speaking of the GWT compiler, we need to invoke it during our
  project's build. How do we teach Maven to do this and other build
  