anchor.diff:  Depending on your use case (library vs. application), you can pick the one that fits your needs.
   The acceptance testing infrastructure is in place for verifying the instrumentation steps, so feel free to contribute a solution ;)
   
  -*Is there a way to dump the instrumented code?*
  -
  -Yes there is!
  -If you add the _-printsource_ flag to the _javac_ call, instead of compiling your application, it will print the instrumented sources.
  -Check the https://github.com/GoodGrind/ghostwriter/blob/master/sample/README.md[sample application README] for a small example.
  -
  -*Is it working with Android based applications?*
  -
  -Not yet but it's very high on our priority list!
  -
   *I put the tracer related jars into my application's classpath, yet they are ignored and noop is selected, why?*
   
   Ghostwriter uses the Java ServiceLoader to find the tracer implementation. In ghostwriter-api 0.4.0, ghostwriter-tracer 0.3.1 and earlier versions
  
positive.code: Set the following environmental variable to track what kind of code GhostWriter writes instead of you.
  
  ----
  GHOSTWRITER_VERBOSE=true
  ----
  
  You should see something like this:
  
negative.code: GHOSTWRITER_EXCLUDE=my.package.SomeClass,my.package.subpackage
  ```
  
  [#method-exl]
  === Excluding methods
  Methods can be also excluded globally by setting GHOSTWRITER_EXCLUDE_METHODS to a comma separated list of method names. For example:
  