Bump version to 2.0.11

Includes the pull request from torax242.

Makes random sleep in PickGreeting configurable.

Author: altenhof

README.md

@@ -26,11 +26,11 @@ All in all, you should do the following:
 * pick your favorite logging implementation, and
 * adjust your logging configuration accordingly.
 
-Say, you want to make use of the *servlet filter* feature, then you need to add the following dependency to your POM with property `cf-logging-version` referring to the latest version (currently `2.0.10`):
+Say, you want to make use of the *servlet filter* feature, then you need to add the following dependency to your POM with property `cf-logging-version` referring to the latest version (currently `2.0.11`):
 
 ```xml
 <properties>
-	<cf-logging-version>2.0.10</cf-logging-version>
+	<cf-logging-version>2.0.11</cf-logging-version>
 </properties>
 ```
 

cf-java-logging-support-core/pom.xml

@@ -24,7 +24,7 @@
   <parent>
     <groupId>com.sap.hcp.cf.logging</groupId>
     <artifactId>cf-java-logging-support-parent</artifactId>
-    <version>2.0.10</version>
+    <version>2.0.11</version>
     <relativePath>../pom.xml</relativePath>
   </parent>
   <profiles>

cf-java-logging-support-jersey/pom.xml

@@ -9,7 +9,7 @@
   	<relativePath>../pom.xml</relativePath>
   	<groupId>com.sap.hcp.cf.logging</groupId>
   	<artifactId>cf-java-logging-support-parent</artifactId>
-  	<version>2.0.10</version>
+  	<version>2.0.11</version>
   </parent>
 
   <name>cf-java-logging-support-jersey</name>

cf-java-logging-support-log4j2/pom.xml

@@ -11,7 +11,7 @@
 		<relativePath>../pom.xml</relativePath>
 		<groupId>com.sap.hcp.cf.logging</groupId>
 		<artifactId>cf-java-logging-support-parent</artifactId>
-		<version>2.0.10</version>
+		<version>2.0.11</version>
 	</parent>
 
 	<properties>

cf-java-logging-support-logback/pom.xml

@@ -10,7 +10,7 @@
   	<relativePath>../pom.xml</relativePath>
   	<groupId>com.sap.hcp.cf.logging</groupId>
   	<artifactId>cf-java-logging-support-parent</artifactId>
-  	<version>2.0.10</version>
+  	<version>2.0.11</version>
   </parent>
 
   <properties>

cf-java-logging-support-servlet/pom.xml

@@ -9,7 +9,7 @@
   <parent>
   	<groupId>com.sap.hcp.cf.logging</groupId>
   	<artifactId>cf-java-logging-support-parent</artifactId>
-  	<version>2.0.10</version>
+  	<version>2.0.11</version>
   	<relativePath>../pom.xml</relativePath>
   </parent>
 

pom.xml

@@ -4,7 +4,7 @@
 
   <groupId>com.sap.hcp.cf.logging</groupId>
   <artifactId>cf-java-logging-support-parent</artifactId>
-  <version>2.0.10</version>
+  <version>2.0.11</version>
   <packaging>pom</packaging>
 
   <name>Cloud Foundry Java logging support components</name>

sample/README.md

@@ -6,6 +6,8 @@ A simple CF sample application that we cloned from [cloudfoundry-sticky-session]
 
 Currently configured to use `log4j2` as the logging implementation.
 
+It uses a environment variable `RANDOM_SLEEP` which, when set to `true` will introduce a artificial delay (up to 1 sec). 
+
 ## Running it locally
 
 You can use the following Maven target to run the application locally 

sample/manifest.yml

@@ -7,4 +7,6 @@ applications:
   host: logging-sample-app
   instances: 1
   memory: 256M
-  path: target/logging-sample-app-2.0.10.war
+  path: target/logging-sample-app-2.0.11.war
+  env:
+    RANDOM_SLEEP: true

sample/pom.xml

@@ -6,7 +6,7 @@
 	<parent>
 		<groupId>com.sap.hcp.cf.logging</groupId>
 		<artifactId>cf-java-logging-support-parent</artifactId>
-		<version>2.0.10</version>
+		<version>2.0.11</version>
 		<relativePath>../pom.xml</relativePath>
 	</parent>
 
@@ -18,7 +18,7 @@
 		<slf4j.version>1.7.12</slf4j.version>
 		<jersey.version>2.22.2</jersey.version>
 		<javax.ws.version>2.0.1</javax.ws.version>
-		<cf-logging.version>2.0.10</cf-logging.version>
+		<cf-logging.version>2.0.11</cf-logging.version>
 	</properties>
 	<dependencies>
 		<dependency>