anchor.diff:  
   ~~~
   
  -Optionally, the buildpack detect script can output additional details decided by the buildpack developer. Such as buildpack versioning information, a detailed list of configured frameworks and their associated versions. The following is an example of the detailed information returned by the Java buildpack:
  +Optionally, the buildpack detect script can output additional details decided by the buildpack developer. These additional details include buildpack versioning information and a detailed list of configured frameworks and their associated versions. 
  +
  +The following is an example of the detailed information returned by the Java buildpack:
   
   ~~~
   java-buildpack=v3.0-https://github.com/cloudfoundry/java-buildpack.git#3bd15e1 open-jdk-jre=1.8.0_45 spring-auto-reconfiguration=1.7.0_RELEASE tomcat-access-logging-support=2.4.0_RELEASE tomcat-instance=8.0.21 tomcat-lifecycle-support=2.4.0_RELEASE ...
  
positive.code: ~~~
  ### <a id='release-script'></a>bin/release ###
  
  The `release` script provides feedback metadata back to Cloud Foundry indicating how the application should be executed. The script is run with one argument, the `build` directory. The script must generate a YAML file in the following format:
  
  ~~~yaml
    default_process_types:
      web: start_command.filetype
  ~~~
  
  `default_process_types` indicates the type of application being run and the command used to start it. At this time only `web` type of applications are supported.
  
  <p class="note"><strong>Note</strong>: To define environment variables for your buildpack, add a bash script to the <code>.profile.d</code> directory in the root folder of your application.</p>
  
  
negative.code: 
  ### <a id='detect-script'></a>bin/detect ###
  
  The `detect` script determines whether or not to apply the buildpack to an application. The script is called with one argument, the `build` directory for the application. The `build` directory contains the application files uploaded when a user performs a `cf push`. 
  
  The `detect` script returns an exit code of `0` if the buildpack is compatible with the application. In the case of system buildpacks, the script also prints the buildpack name, version, and other helpful information to `STDOUT`. 
  
  The following is an example `detect` script written in Ruby that checks for a Ruby application based on the existence of a `Gemfile`:
  
  ~~~ruby
  
  