anchor.diff:  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 %>).
  +<% current_page.data.title = "How Buildpacks Work in " + vars.product_short %>
  +
  +This topic describes how buildpacks are structured and detected in <%= vars.product_runtime %> (<%= vars.product_short %>).
   
   
   ## <a id='buildpack-scripts'></a> Buildpack Scripts
  
positive.code: 
  ### <a id='detection'></a> Buildpack Detection
  
  <%= vars.app_runtime_abbr %> performs buildpack detection if the developer does not specify one or more buildpacks in the app manifest or in the `cf push APP-NAME -b BUILDPACK-NAME` cf CLI command.
  
  <p class="note"><strong>Note:</strong> <%= vars.app_runtime_abbr %> detects only one buildpack to use with the app.</p>
  
  If the platform performs detection, it:
  
  
negative.code: 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>
  
  For more information, see [Buildpack Detection](#buildpack-detection).
  
  