anchor.diff:  * The Gremlin `ScriptEngine` instances to expose and external dependencies to inject into them
   * `Graph` instances to expose
   
  -The log messages that printed above show a number of things, but most importantly, there is a `Graph` instance named `g` that is exposed in Gremlin Server.  This graph is an in-memory TinkerGraph and was empty at the start of the server.  An initialization script at `scripts/generate-sample.groovy` was executed during startup.  It's contents are as follows:
  -
  -[source,groovy]
  -----
  -include::../gremlin-server/scripts/generate-modern.groovy[]
  -----
  -
  -This script loads the "modern" graph into the empty TinkerGraph instance, preparing it for use.  With Gremlin Server running it is now possible to issue some scripts to it for processing.  Start Gremlin Console as follows:
  +The log messages that printed above show a number of things, but most importantly, there is a `Graph` instance named `g` that is exposed in Gremlin Server.  This graph is an in-memory TinkerGraph and was empty at the start of the server.  An initialization script at `scripts/generate-classic.groovy` was executed during startup.  It's contents are as follows:
  +
  +[source,groovy]
  +----
  +include::../gremlin-server/scripts/generate-classic.groovy[]
  +----
  +
  +This script loads the "classic" graph into the empty TinkerGraph instance, preparing it for use.  With Gremlin Server running it is now possible to issue some scripts to it for processing.  Start Gremlin Console as follows:
   
   [source,text]
   ----
  
positive.code: 
  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.
  
  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:
  
  
negative.code: 
  [source,groovy]
  ----
  gremlin> :install com.tinkerpop neo4j-gremlin 3.0.0-SNAPSHOT
  ==>loaded: [com.tinkerpop, neo4j-gremlin, 3.0.0-SNAPSHOT]
  gremlin> :plugin use neo4j
  ==>...
  ==>neo4j activated
  gremlin> g = Neo4jGraph.open('/tmp/neo4j')
  ==>neo4jgraph[EmbeddedGraphDatabase [/tmp/neo4j]]
  ----
  