anchor.diff:  Java applications can be packaged as Servlet applications.
   
   ### <a id='servlet-maven'></a>Maven ###
  -A Maven build can create a Servlet WAR. To build and deploy the WAR, run the following:
  +A Maven build can create a Servlet WAR.
  +To build and deploy the WAR, run the following:
   
   <pre class="terminal">
   $ mvn package
   $ cf push &lt;application-name&gt; -p target/&lt;application-name&gt;-&lt;application-version&gt;.war
   </pre>
   
  -
   ### <a id='servlet-gradle'></a>Gradle ###
  -A Gradle build can create a Servlet WAR. To build and deploy the JAR, run the following:
  +A Gradle build can create a Servlet WAR.
  +To build and deploy the JAR, run the following:
   
   <pre class="terminal">
   $ gradle build
  
positive.code: 
  ## <a id='configuration'></a>Configuration ##
  In most cases, the buildpack should work without any configuration.
  If you are new to Cloud Foundry, we recommend that you make your first attempts without modifying the buildpack configuration.
  If the buildpack requires some configuration, use [a fork of the buildpack][f].
  
  ## <a id='java-apps'></a>Java and Grails Best Practices ##
  
negative.code: 
  ### <a id='memory'></a>Allocate Sufficient Memory ###
  
  If you do not allocate sufficient memory to a Java application when you deploy
  it, it may fail to start, or <%=vars.product_short%> may terminate it.
  You must allocate enough memory to allow for the following:
  
  * Java heap
  * Metaspace, if using Java 8
  