anchor.diff:  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.
   
  
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: 
  After finishing all tasks, the script will immediately destroy the container.
  
  Docker based builds can be helpful to developers who do not want to setup a full Maven environment, which may be the
  case for developers doing work on Gremlin Language Variants (e.g. Python). It allows them a way to do a full build of
  the entire project to be sure that their changes are valid. Developers can also start Gremlin Server with its standard
  test configuration:
  
  [source,bash]
  docker/build.sh -t
  
  Starting Gremlin Server this way makes it possible to run Gremlin Language Variant tests without Maven (for example,
  directly from a debugger) which should greatly reduce development friction for these environments.
  
  == IDE Setup with Intellij
  
  