anchor.diff:      |_tmp
   ```
   
  -In the case of `ruby` plugin (and as mentionned before), the correct version of the `jruby.jar` must exist (and be name that way) under the `platform` directory entry. The correct version must match the Kill Bill version (or more precisely the version of the https://github.com/killbill/killbill-platform[platform] used for the a specific version of https://github.com/killbill/killbill[killbill]).
  -
  -
  +In order to make it easy to deploy those plugins we created a special rake task that will copy, untar plugin entries at the right place:
  +
  +[source,ruby]
  +----
  +# Optional: deploy the plugin (and clobber a previous version if needed) in /var/tmp/bundles.
  +# Alternatively, you can manualy deploy the .tar.gz or .zip artifact from the pkg/ directory
  +bundle exec rake killbill:deploy[true]
  +----
  +
  +Note that if you don't need any custom configuration, make sure to delete the default YAML configuration file `/var/tmp/bundles/plugins/ruby/killbill-\*/*/*.yml`. In development mode, i.e. when you are running tests outside of Kill Bill (see `rake test:spec` and `rake test:remote:spec`), the database configuration is specified in that YAML file (payment plugins rely on a couple of database tables, principally to keep the credit card tokens and gateway-specific details for transactions, such as reference codes). By default, the plugin will use SQLite. If you uncomment the part of the YAML file below the comment "In Kill Bill", this will tell the plugin to use the JNDI connection exposed by Kill Bill instead. This is the default in case the file isn't present (or if the database section is missing).
  +
  +
  +Also, in the case of `ruby` plugin (and as mentionned before), the correct version of the `jruby.jar` must exist (and be name that way) under the `platform` directory entry. The correct version must match the Kill Bill version (or more precisely the version of the https://github.com/killbill/killbill-platform[platform] used for the a specific version of https://github.com/killbill/killbill[killbill]).
   
   
   === KPM
  
positive.code: == Deployment
  
  === Overview
  
  In its simplest form, deploying a plugin means placing the plugin binary at the right place on the filesystem. Kill Bill will scan the filesystem on startup and will start all the plugins that were detected.
  Kill Bill will use the value of the system property `org.killbill.osgi.bundle.install.dir` to determine the root of plugin directory structure.
  
negative.code: 
  The file `plugin_identifiers.json` is used to keep a mapping between the `pluginKey` (the user visible plugin identifer), and the `pluginName` (runtime identifier used by Kill Bill when scanning the filesystem). The next section provides more details about those.
  
  ==== Plugin Coordinates, Plugin Key, Plugin Name...
  
  Today, both our `ruby` and `java` plugins are released through maven and are therefore identified through their maven coordinates.
  We might support other schemes in the future but today this is the only way we offer to download and install publicly released plugins.
  