diff --git a/pom.xml b/pom.xml
index 004c98e4e..a35752663 100644
--- a/pom.xml
+++ b/pom.xml
@@ -180,22 +180,6 @@
                <showDeprecation>true</showDeprecation>
             </configuration>
          </plugin>
-         <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 
-               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>
-            <version>1.6.5</version>
-            <extensions>true</extensions>
-            <configuration>
-               <serverId>ossrh</serverId>
-               <nexusUrl>https://oss.sonatype.org/</nexusUrl>
-               <autoReleaseAfterClose>false</autoReleaseAfterClose>
-            </configuration>
-         </plugin>
          <plugin>
             <groupId>com.mycila</groupId>
             <artifactId>license-maven-plugin</artifactId>
@@ -413,6 +397,35 @@
       </pluginManagement>
    </build>
    <profiles>
+      <profile>
+         <id>nexus_staging</id>
+         <activation>
+            <activeByDefault>true</activeByDefault>
+            <property>
+               <name>useNexusStaging</name>
+            </property>
+         </activation>
+         <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 skipStaging=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>
+                  <version>1.6.5</version>
+                  <extensions>true</extensions>
+                  <configuration>
+                     <serverId>ossrh</serverId>
+                     <nexusUrl>https://oss.sonatype.org/</nexusUrl>
+                     <autoReleaseAfterClose>false</autoReleaseAfterClose>
+                  </configuration>
+               </plugin>
+            </plugins>
+         </build>
+      </profile>
       <profile>
          <!-- this profile generates GPG signatures -->
          <id>create_gpg_signature</id>