anchor.diff:  
   You can access environments variable programmatically.
   
  -For example, you can obtain `VCAP_SERVICES` like this:
  +For example, you can obtain `VCAP_SERVICES` as follows:
   
   ```
   System.getenv("VCAP_SERVICES");
   ```
   
   The environment variables you can access are those [defined by the DEA]
  -(../../devguide/deploy-apps/environment-variable.html#dea-set).
  -
  +(../../devguide/deploy-apps/environment-variable.html#dea-set).
positive.code: * Thread stacks
  * JVM overhead
  
  The `config/open_jdk_jre.yml` file of the [Cloud Foundry Java buildpack](https://github.com/cloudfoundry/java-buildpack) contains default memory size and weighting settings for the JRE. See the [Open JDK JRE README](https://github.com/cloudfoundry/java-buildpack/blob/master/docs/jre-open_jdk_jre.md) on GitHub for an explanation of JRE memory sizes and weightings and how the Java buildpack calculates and allocates memory to the JRE for your app.
  
  To configure memory-related JRE options for your app, you create a custom buildpack and specify this buildpack in your deployment manifest. For more information on configuring custom buildpacks and manifests, refer to the [Custom Buildpacks](../../buildpacks/custom.html) and [Deploying with Application Manifests](../../devguide/deploy-apps/manifest.html) topics.
  
  When your app is running, you can use the `cf app [APP_NAME]` command to see memory utilization.
  
  ### <a id='upload'></a>Troubleshoot Failed Upload ###
  
  
negative.code: </pre>
  
  ### <a id='raw-groovy'></a>Raw Groovy ###
  Groovy applications that are made up of a [single entry point][g] plus any
  supporting files can be run without any other work.
  To deploy them, run the following:
  
  <pre class="terminal">
  $ cf push &lt;application-name&gt;
  </pre>
  
  ## <a id='java-main'></a>Java Main ##
  Java applications with a `main()` method can be run provided that they are
  packaged as [self-executable JARs][j].
  
  ### <a id='java-main-maven'></a>Maven ###
  A Maven build can create a self-executable JAR.
  To build and deploy the JAR, run the following:
  
  <pre class="terminal">
  $ mvn package
  $ cf push &lt;application-name&gt; -p target/&lt;application-name&gt;-&lt;application-version&gt;.jar
  </pre>
  
  ### <a id='java-main-gradle'></a>Gradle ###
  A Gradle build can create a self-executable JAR.
  To build and deploy the JAR, run the following:
  
  <pre class="terminal">
  $ gradle build
  $ cf push &lt;application-name&gt; -p build/libs/&lt;application-name&gt;-&lt;application-version&gt;.jar
  </pre>
  
  ## <a id='play-framework'></a>Play Framework ##
  The [Play Framework][p] packages applications into two different styles.
  Cloud Foundry supports both the `staged` and `dist` styles. To build the `dist`
  style and deploy it, run the following:
  
  <pre class="terminal">
  $ play dist
  