anchor.diff:  One of the most important things to know about developing a Forge addon, is that the Furnace runtime container (the core of Forge),
   is actually an embeddable, modular Java container. This means that each addon has its own `ClassLoader` and that
   addons share classes from each other, in addition to supplying their own local classes. Furnace builds a graph of
  -addon dependencies at runtime, and automatically calculates which addons should see classes from other addons. 
  +addon dependencies at runtime, and automatically calculates which addons should see classes from other addons.
   
   For now, however, just treat your first addon as if it were any other Java project. The differences between a "modular" and
   "traditional" environment are not as great as you might think, and the Furnace development model has been created in
  -a way that should make these differences seem natural, almost transparent. 
  +a way that should make these differences seem natural, almost transparent.
   
   === Create a Maven project
   
  
positive.code:          <scope>provided</scope>
        </dependency>
  
        <!-- Furnace Container -->   
        <dependency>
           <groupId>org.jboss.forge.furnace.container</groupId>
           <artifactId>cdi</artifactId>
  
negative.code: The fastest way to build applications, share your software, and enjoy doing it.
  
  
  What's new and noteworthy?
  --------------------------
  
  - *Addons*: What were previously called "Plugins" in Forge 1, are now "Addons" in Forge 2. This decision was made to clear up confusing verbiage like, "Plugin X has N Plugins" (due to the org.jboss.forge.plugins.Plugin interface.)
  