From 25209166a7da1e08406040b26914d17482f6c51e Mon Sep 17 00:00:00 2001
From: Dominic Schabel <dominic.schabel@bosch-si.com>
Date: Mon, 17 Dec 2018 15:56:11 +0100
Subject: [PATCH] Fixed outdated comment

Signed-off-by: Dominic Schabel <dominic.schabel@bosch-si.com>
---
 pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pom.xml b/pom.xml
index a3ecc2159..2ae21221a 100644
--- a/pom.xml
+++ b/pom.xml
@@ -507,7 +507,7 @@
                <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 skipStaging=true/false. In any case we can take advantage of the plugin's "deferred deploy" feature which makes sure that
+                     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>