anchor.diff:  <pre>
   ---
     ...
  -  buildpack: buildpack_URL
  -</pre>
  +  buildpacks: 
  +    - buildpack_URL
  +</pre>
  +
  +If you are using multiple buildpacks, you can provide an additional `-b` flag or add an additional value to your manifest:
  +
  +<pre>
  +---
  +  ...
  +  buildpacks: 
  +    - buildpack_URL
  +    - buildpack_URL
  +</pre>
  +
  +<p class="note"><strong>Note</strong>: You must specify multiple buildpacks in the correct order: the buildpack will use the app start command given by the final buildpack. See <a href=https://github.com/cloudfoundry/multi-buildpack#usageapp</a> for more information.</p>
  +
  +Also see [Pushing an Application with Multiple Buildpacks](https://docs.cloudfoundry.org/buildpacks/use-multiple-buildpacks.html) for more information. 
  +
   
   <p class="note"><strong>Note</strong>: The <code>cf buildpacks</code> command lists the buildpacks that you can refer to by name in a manifest or a command line option.</p>
   
  
positive.code: <pre>
  ---
  defaults: &amp;defaults
    buildpack: staticfile_buildpack
    memory: 1G
  
  applications:
  
negative.code: 
  <p class='note'><strong>Note:</strong> The route component attributes <code>domain</code>, <code>domains</code>, <code>host</code>, <code>hosts</code>, and <code>no-hostname</code> have been deprecated in favor of the <code>routes</code> attribute. For more information, see <a href=#deprecated>Deprecated App Manifest Features</a>.</p>
  
  ### <a id='buildpack'></a> buildpacks
  
  If your application requires a custom buildpack, you can use the `buildpacks` attribute to specify it in a number of ways:
  
  * By name: `MY-BUILDPACK`. 
  * By GitHub URL: `https://github.com/cloudfoundry/java-buildpack.git`. 
  