anchor.diff:  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 ...
   ```
   
  -<p class="note"><strong>Note:</strong> <%= vars.product_short %> detects only one buildpack by default. When multiple buildpacks are desired, you must explicitly specify them.</p>
  +<p class="note"><strong>Note:</strong> <%= vars.app_runtime_abbr %> detects only one buildpack by default. When multiple buildpacks are desired, you must explicitly specify them.</p>
   
   For more information, see [Buildpack Detection](#buildpack-detection).
   
  
positive.code: 
  ### <a id='release-script'></a> bin/release
  
  The `release` script provides feedback metadata to <%= vars.product_short %> indicating how the app should be executed. The script is run with one argument, the `build` directory. The script must generate a YAML file in the following format:
  
  ```
  default_process_types:
  
negative.code: owner: Buildpacks
  ---
  
  <% current_page.data.title = "How Buildpacks Work in " + vars.app_runtime_abbr %>
  
  This topic describes how buildpacks are structured and detected in <%= vars.app_runtime_full %> (<%= vars.app_runtime_abbr %>).
  
  
  ## <a id='buildpack-scripts'></a> Buildpack Scripts
  