diff --git a/pom.xml b/pom.xml
index 9f4dd376a..09699122e 100644
--- a/pom.xml
+++ b/pom.xml
@@ -128,12 +128,12 @@
 
    <properties>
       <java.version>1.8</java.version>
-      <spring.boot.version>2.1.3.RELEASE</spring.boot.version>
+      <spring.boot.version>2.1.4.RELEASE</spring.boot.version>
       <spring.cloud.version>Greenwich.RELEASE</spring.cloud.version>
 
       <snapshotDependencyAllowed>true</snapshotDependencyAllowed>
 
-      <!-- Spring boot version overrides (should be reviewed with every boot 
+      <!-- Spring boot version overrides (should be reviewed with every boot
          upgrade) - START -->
       <!-- Newer versions needed than defined in Boot -->
       <!-- Fixed dependencies -->
@@ -222,8 +222,8 @@
             <artifactId>maven-enforcer-plugin</artifactId>
             <executions>
                <execution>
-                  <!-- Make sure that only non-snapshot versions are used 
-                     for the dependencies. Only active when property 'snapshotDependencyAllowed' 
+                  <!-- Make sure that only non-snapshot versions are used
+                     for the dependencies. Only active when property 'snapshotDependencyAllowed'
                      is false. -->
                   <id>enforce-no-snapshots</id>
                   <goals>
@@ -480,14 +480,14 @@
          <build>
             <plugins>
                <plugin>
-                  <!-- Use the Nexus Staging plugin as a full replacement 
-                     for the standard Maven Deploy plugin. See https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin 
-                     why this makes sense :-) We can control whether we want to deploy to the 
-                     Eclipse repo or Maven Central by a combination of the version being a SNAPSHOT 
-                     or RELEASE version and property skipNexusStaging=true/false. In any case 
-                     we can take advantage of the plugin's "deferred deploy" feature which makes 
-                     sure that all artifacts of a multi-module project are deployed as a whole 
-                     at the end of the build process instead of deploying each module's artifacts 
+                  <!-- Use the Nexus Staging plugin as a full replacement
+                     for the standard Maven Deploy plugin. See https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin
+                     why this makes sense :-) We can control whether we want to deploy to the
+                     Eclipse repo or Maven Central by a combination of the version being a SNAPSHOT
+                     or RELEASE version and property skipNexusStaging=true/false. In any case
+                     we can take advantage of the plugin's "deferred deploy" feature which makes
+                     sure that all artifacts of a multi-module project are deployed as a whole
+                     at the end of the build process instead of deploying each module's artifacts
                      individually as part of building the module. -->
                   <groupId>org.sonatype.plugins</groupId>
                   <artifactId>nexus-staging-maven-plugin</artifactId>