anchor.diff:  
   == Developing an Addon
   
  -Forge addons are simple Maven projects with a special classifier "forge-addon". This classifier is used while installing an addon so Forge can calculate its dependencies automatically releasing you from the http://robjsoftware.org/2007/07/13/classloader-hell/[Classloader hell]
  +Forge addons are simple Maven projects with a special classifier "forge-addon". This classifier is used while installing an addon so the Furnace container can calculate its dependencies, freeing you from http://robjsoftware.org/2007/07/13/classloader-hell/[Classloader hell].
  +
  +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. 
  +
  +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. 
   
   === Create a Maven project
   
  -Forge Addons must be packaged with a 'forge-addon' classifier. Add this plugin configuration to your pom.xml:
  +Forge Addons must be JARs published with a 'forge-addon' classifier. Add this plugin configuration to your pom.xml:
   
   [source,xml]
   ----
  -    <build>
  +<build>
  +   <plugins>
  +      <plugin>
  +         <groupId>org.apache.maven.plugins</groupId>
  +         <artifactId>maven-jar-plugin</artifactId>
  +         <executions>
  +            <execution>
  +               <id>create-forge-addon</id>
  +               <phase>package</phase>
  +               <goals>
  +                  <goal>jar</goal>
  +               </goals>
  +               <inherited>false</inherited>
  +               <configuration>
  +                  <classifier>forge-addon</classifier>
  +               </configuration>
  +            </execution>
  +         </executions>
  +      </plugin>
  +   </plugins>
  +</build>
  +----
  +
  +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:
  +
  +[source,xml]
  +----
  +<dependency>
  +   <groupId>org.jboss.forge.furnace</groupId>
  +   <artifactId>container-cdi</artifactId>
  +   <classifier>forge-addon</classifier>
  +   <scope>provided</scope>
  +</dependency>
  +----
  +
  +Your complete POM should now look something like this:
  +
  +[source,xml]
  +----
  +<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  +   <modelVersion>4.0.0</modelVersion>
  +
  +   <groupId>com.example</groupId>
  +   <artifactId>example</artifactId>
  +   <version>0.0.1-SNAPSHOT</version>
  +   
  +   <name>My First Addon</name>
  +
  +   <dependencies>
  +      <dependency>
  +         <groupId>org.jboss.forge.furnace</groupId>
  +         <artifactId>container-cdi</artifactId>
  +         <classifier>forge-addon</classifier>
  +         <scope>provided</scope>
  +      </dependency>
  +   </dependencies>
  +
  +   <build>
         <plugins>
            <plugin>
               <groupId>org.apache.maven.plugins</groupId>
  
positive.code:             </executions>
           </plugin>
        </plugins>
      </build>
  ----
  
  === Use the Forge CDI Container
  
  In order to use CDI in your addon, you need to reference the Furnace CDI container addon in your _pom.xml_ file:
  
  [source,xml]
  ----
  <dependency>
     <groupId>org.jboss.forge.furnace</groupId>
     <artifactId>container-cdi</artifactId>
     <classifier>forge-addon</classifier>
     <scope>provided</scope>
  </dependency>
  ----
  
  Once this is done, to expose services in your Addon for injection and service lookups in other addons, your types must be annotated with **@Exported**: 
  
  [source,java]
  ----
      @Exported
      public class ServiceImpl
      {
         public ServiceResult performTask() {
              // Do stuff...
         }
      }
  ----
  
  However, best practices favor placing the **@Exported** annotation on a service interface, otherwise consumers will be required to request your specific service implementation. For example:
  
  [source,java]
  ----
      @Exported
      public interface ServiceType
      {
         public ServiceResult performTask();
      }
  ----
  
  Then simply implement the service interface, and the **@Exported** annotation will be inherited automatically:
  
  [source,java]
  ----
      public class ServiceImpl implements ServiceType
      {
         public ServiceResult performTask() {
              // Do stuff...
         }
      }
  ----
  
  === Install your project in the local maven repository:
  
  [source,cmd]
  ----
  
negative.code:     ./forge --install yourgroupId:artifactId,version
  ----
  
  WARNING: This coordinate is *NOT* the same as maven's. You MUST use a comma (,) between the artifactId and the version**
  
  === Install your Addon
   
  