anchor.diff:  ** The test suite for `neo4j-gremlin` is disabled by default - to turn it on: `mvn clean install -DincludeNeo4j`
   * Regenerate test data (only necessary given changes to IO classes): `mvn clean install -Dio` from `tinkergraph-gremlin` directory
   ** If there are changes to the Gryo format, it may be necessary to generate the Grateful Dead dataset from GraphSON (see `IoDataGenerationTest.shouldWriteGratefulDead`)
  +* Start Gremlin Server with Docker using the standard test configuration: `docker/gremlin-server.sh`
   * Check license headers are present: `mvn apache-rat:check`
   * Build AsciiDocs (see <<documentation-environment,Documentation Environment>>): `bin/process-docs.sh`
   ** Build AsciiDocs (but don't evaluate code blocks): `bin/process-docs.sh --dryRun`
  
positive.code: [source,text]
  mvn clean install -pl gremlin-console -DskipIntegrationTests=false
  
  See the <<release-environment,Release Environment>> section for more information on release manager configurations.
  
  [[dotnet-environment]]
  
negative.code: When building `gremlin-javascript`, mvn command will include a local copy of Node.js runtime and npm inside your project
  using `com.github.eirslett:frontend-maven-plugin` plugin. This copy of the Node.js runtime will not affect any
  other existing Node.js runtime instances in your machine.
  
  TIP: For those who do not have a full Maven environment, please see <<docker-integration,this section>> for how Docker
  can be used to help run tests.
  
  See the <<release-environment,Release Environment>> section for more information on release manager configurations.
  
  