anchor.diff:  }
   ---- 
   
  -Now that the test case deploys and depends on your addon, you may access services from it via injection:
  +Now that the test case deploys and depends on your addon, you may access services from it via injection (because your test deployment also depends on the Furnace CDI container):
   
   [source,java]
   ----
  
positive.code:    ...
     
     <dependencies>
        <!-- Addon Dependencies -->
        <dependency>
           <groupId>org.jboss.forge.addon</groupId>
  
negative.code: </build>
  ----
  
  ---- Add a Furnace container
  
  _(Skip this step if you used the `Project: New` command from the previous step.)_
  
  In order to use CDI and services from other addons in your addon, you'll need to reference the Furnace CDI container addon as a dependency your _pom.xml_ file. Your choice of default Furnace container (CDI or Simple) will control your addon's lifecycle.
  
  You may also choose to omit a Furance container - this means your addon will not produce any services, will not start any jobs, and can only be used as a modular library by other addons. Alternatively, you can implement your own Furnace container, but that is a discussion for link:https://github.com/forge/furnace/blob/master/container-api/src/main/java/org/jboss/forge/furnace/lifecycle/AddonLifecycleProvider.java#L20[another document].
  
  [source,xml]
  ----
  