anchor.diff:  
   Once the plugin is packaged, there are two ways to test it out:
   
  -. Copy the jar and its dependencies to the Gremlin Console path and start it.  The plugin should show its name as one of the ones that was loaded at startup.
  -. Start Gremlin Console and try the `:use` command.  For the case of the Neo4j plugin, it would look like this: `:use now com.tinkerpop neo4j-gremlin 3.y.z`.
  -
  -In either case, once one of these two approaches is taken, the Neo4j classes should be available for use within the console.
  +. Copy the jar and its dependencies to the Gremlin Console path and start it.
  +. Start Gremlin Console and try the `:install` command.  For the case of the Neo4j plugin, it would look like this: `:install com.tinkerpop neo4j-gremlin 3.y.z`.
  +
  +In either case, once one of these two approaches is taken, the jars and their dependencies are available to the Console.  The next step is to "activate" the plugin by doing `:plugin use neo4j`, where "neo4j" refers to the name of the plugin to activate.
   
   A plugin can do much more than just import classes.  One can expand the Gremlin language with new functions or steps, provide useful commands to make repetitive or complex tasks easier to execute, or do helpful integrations with other systems.  The secret to doing so lies in the `PluginAcceptor`.  As mentioned earlier, the `PluginAcceptor` provides access to the host of the plugin.  It provides several important methods for doing so:
   
  
positive.code:          \,,,/
           (o o)
  -----oOOo-(3)-oOOo-----
  plugin loaded: server
  plugin loaded: gephi
  plugin loaded: utilities
  plugin loaded: giraph
  gremlin>
  ----
  
  Properties Files
  
negative.code:          \,,,/
           (o o)
  -----oOOo-(3)-oOOo-----
  plugin activated: server
  plugin activated: utilities
  gremlin> :install com.tinkerpop giraph-gremlin 3.0.0
  ==>loaded: [com.tinkerpop, giraph-gremlin, 3.0.0] - restart the console to use [giraph]
  gremlin> :q
  $ bin/gremlin.sh
  