anchor.diff:  | Description
   
   | `IPolicyFailureFactoryComponent`
  -| Used to create a policy failure that is needed to call 'doFailure' on the policy chain (indicating that the policy failed).
  +| Used to create a policy failure that is needed to call `doFailure` on the policy chain (indicating that the policy failed).
   
   | `ISharedStateComponent`
   | Used to share state information across the conversation boundary.
  
positive.code: === Import the Framework (Maven Dependency)
  
  The first thing you will need is to include the appropriate maven dependencies in your project's `pom.xml` file.
  There is a single additional dependency that you will need (make sure to import it using the 'test' maven scope):
  
  [source,xml,subs=attributes+]
  ----
  
negative.code: META-INF/apiman/plugin.json
  ----
  
  This `plugin.json` file contains the basic meta-data that describes the plugin, and should be of the following format:
  
  [source,json]
  ----
  {
    "frameworkVersion" : 1.0, // <1>
    "name" : "Plugin Name", // <2>
    "description" : "A plugin description goes here.", // <3>
    "version" : "3.1.9" // <4>
  }
  ----
  
  <1> *frameworkVersion*: Indicates the apiman plugin framework version this plugin is compatible with - this should simply be 1.0 for now (reserved for future use)
  
  <2> *name*: The name of the plugin.
  <3> *description*: The description of the plugin.
  <4> *version*: The plugin version.
  
  If this `plugin.json` file is missing from the plugin archive, then the plugin will fail to load.
  
  [#_using_maven_to_create_a_plugin]
  == Using Maven to Create a Plugin
  