anchor.diff:     <groupId>com.example</groupId>
      <artifactId>example</artifactId>
      <version>0.0.1-SNAPSHOT</version>
  -   
  +
      <name>My First Addon</name>
   
      <dependencies>
  
positive.code: 
  The `Facet` class comes from the `facets` addon and is used in the public APIs of your addon.
  
  |===   
  
   
  
  === Test your addon
  
  
negative.code:       Assert.assertNotNull(service.doSomething());
     }
  }
  ----
  
  This is the basic premise of using the test-harness. For detailed examples, take a
  https://github.com/forge/core/tree/master/resources/tests/src/test/java/org/jboss/forge/addon/resource[look at some of the existing
  Forge test cases] in our github repository.
  
  NOTE: The `version` parameter in `@AddonDependency` and in the `AddonDependencyEntry.create(...)` method are optional. By not specifying them means that the test harness
  will attempt to find the version based on the tests' build descriptor (pom.xml). In this case, if the dependent addon is not present in the tests' build descriptor, the test execution should fail.
  
  === Install your addon in the local maven repository:
  