Consistent javadoc "code" block formatting

Update javadoc to consistently use the "code" style with <pre> blocks.
Also include the latest spring-javadoc.css formatting file.

Fixes gh-332

spring-boot-docs/pom.xml

@@ -56,6 +56,12 @@
 										<dependencySourceInclude>${project.groupId}:*</dependencySourceInclude>
 									</dependencySourceIncludes>
 									<attach>false</attach>
+									<quiet>true</quiet>
+									<stylesheetfile>${basedir}/src/main/javadoc/spring-javadoc.css</stylesheetfile>
+									<links>
+										<link>http://docs.spring.io/spring-framework/docs/4.0.x/javadoc-api/</link>
+										<link>http://docs.oracle.com/javase/7/docs/api/</link>
+									</links>
 								</configuration>
 							</execution>
 						</executions>

spring-boot/src/main/java/org/springframework/boot/builder/SpringApplicationBuilder.java

@@ -42,14 +42,14 @@ import org.springframework.core.io.ResourceLoader;
  * convenient fluent API and context hierarchy support. Simple example of a context
  * hierarchy:
  * 
- * <pre>
+ * <pre class="code">
  * new SpringApplicationBuilder(ParentConfig.class).child(ChildConfig.class).run(args);
  * </pre>
  * 
  * Another common use case is setting default arguments, e.g. active Spring profiles, to
  * set up the environment for an application:
  * 
- * <pre>
+ * <pre class="code">
  * new SpringApplicationBuilder(Application.class).profiles(&quot;server&quot;)
  * 		.defaultArgs(&quot;--transport=local&quot;).run(args);
  * </pre>

spring-boot/src/main/java/org/springframework/boot/cloudfoundry/VcapApplicationListener.java

@@ -49,7 +49,7 @@ import org.springframework.util.StringUtils;
  * index, etc.), and VCAP_SERVICES is a hash of lists where the keys are service labels
  * and the values are lists of hashes of service instance meta data. Examples are:
  * 
- * <pre>
+ * <pre class="code">
  * VCAP_APPLICATION: {"instance_id":"2ce0ac627a6c8e47e936d829a3a47b5b","instance_index":0,
  *   "version":"0138c4a6-2a73-416b-aca0-572c09f7ca53","name":"foo",
  *   "uris":["foo.cfapps.io"], ...}
@@ -66,7 +66,7 @@ import org.springframework.util.StringUtils;
  * instance name (e.g. "mysql" in the example above), and value equal to that instances
  * properties, and then flattened in the same way. E.g.
  * 
- * <pre>
+ * <pre class="code">
  * vcap.application.instance_id: 2ce0ac627a6c8e47e936d829a3a47b5b
  * vcap.application.version: 0138c4a6-2a73-416b-aca0-572c09f7ca53
  * vcap.application.name: foo

spring-boot/src/main/java/org/springframework/boot/yaml/YamlMapFactoryBean.java

@@ -31,7 +31,7 @@ import org.springframework.beans.factory.FactoryBean;
  * is all entries with the same nested key of type Map at any depth are merged. For
  * example:
  * 
- * <pre>
+ * <pre class="code">
  * foo:
  *   bar:
  *    one: two
@@ -41,7 +41,7 @@ import org.springframework.beans.factory.FactoryBean;
  * 
  * plus (later in the list)
  * 
- * <pre>
+ * <pre class="code">
  * foo:
  *   bar:
  *    one: 2
@@ -51,7 +51,7 @@ import org.springframework.beans.factory.FactoryBean;
  * 
  * results in an effecive input of
  * 
- * <pre>
+ * <pre class="code">
  * foo:
  *   bar:
  *    one: 2

spring-boot/src/main/java/org/springframework/boot/yaml/YamlProcessor.java

@@ -54,7 +54,7 @@ public class YamlProcessor {
 	 * documents in a YAML resource. In YAML documents are separated by
 	 * <code>---<code> lines, and each document is converted to properties before the match is made. E.g.
 	 * 
-	 * <pre>
+	 * <pre class="code">
 	 * environment: dev
 	 * url: http://dev.bar.com
 	 * name: Developer Setup
@@ -67,7 +67,7 @@ public class YamlProcessor {
 	 * when mapped with <code>documentMatchers = YamlProcessor.mapMatcher({"environment": "prod"})</code>
 	 * would end up as
 	 * 
-	 * <pre>
+	 * <pre class="code">
 	 * environment=prod
 	 * url=http://foo.bar.com
 	 * name=My Cool App

spring-boot/src/main/java/org/springframework/boot/yaml/YamlPropertiesFactoryBean.java

@@ -28,7 +28,7 @@ import org.springframework.beans.factory.FactoryBean;
  * The Properties created by this factory have nested paths for hierarchical objects, so
  * for instance this YAML
  * 
- * <pre>
+ * <pre class="code">
  * environments:
  *   dev:
  *     url: http://dev.bar.com
@@ -40,7 +40,7 @@ import org.springframework.beans.factory.FactoryBean;
  * 
  * is transformed into these Properties:
  * 
- * <pre>
+ * <pre class="code">
  * environments.dev.url=http://dev.bar.com
  * environments.dev.name=Developer Setup
  * environments.prod.url=http://foo.bar.com
@@ -50,7 +50,7 @@ import org.springframework.beans.factory.FactoryBean;
  * Lists are represented as comma-separated values (useful for simple String values) and
  * also as property keys with <code>[]</code> dereferencers, for example this YAML:
  * 
- * <pre>
+ * <pre class="code">
  * servers:
  * - dev.bar.com
  * - foo.bar.com
@@ -58,7 +58,7 @@ import org.springframework.beans.factory.FactoryBean;
  * 
  * becomes java Properties like this:
  * 
- * <pre>
+ * <pre class="code">
  * servers=dev.bar.com,foo.bar.com
  * servers[0]=dev.bar.com
  * servers[1]=foo.bar.com