diff --git a/auto-pipeline-examples/pom.xml b/auto-pipeline-examples/pom.xml
index 8b5a893..ff66582 100644
--- a/auto-pipeline-examples/pom.xml
+++ b/auto-pipeline-examples/pom.xml
@@ -51,4 +51,24 @@
 			<scope>provided</scope>
 		</dependency>
 	</dependencies>
+
+	<build>
+		<plugins>
+			<plugin>
+				<!--
+				If you are deploying to Maven Central, it is the Nexus Staging Plugin that is
+				doing the deployment instead of the Deploy plugin,
+				so the configuration of the deploy plugin has no effect.
+				To make the Nexus deploy plugin skip, set skipNexusStagingDeployMojo
+				in its configuration to true.
+				-->
+				<!-- see: https://stackoverflow.com/questions/59552549/preventing-maven-modules-from-being-deployed -->
+				<groupId>org.sonatype.plugins</groupId>
+				<artifactId>nexus-staging-maven-plugin</artifactId>
+				<configuration>
+					<skipNexusStagingDeployMojo>true</skipNexusStagingDeployMojo>
+				</configuration>
+			</plugin>
+		</plugins>
+	</build>
 </project>
diff --git a/auto-pipeline-processor/pom.xml b/auto-pipeline-processor/pom.xml
index 0b70489..ef91f20 100644
--- a/auto-pipeline-processor/pom.xml
+++ b/auto-pipeline-processor/pom.xml
@@ -67,6 +67,16 @@
 	<profiles>
 		<profile>
 			<id>gen-doc</id>
+			<!--
+			Profiles are not inherited from parent pom
+			see: https://stackoverflow.com/questions/46681281/maven-active-by-default-profile-in-parent-does-not-propagate-to-children
+			-->
+			<activation>
+				<property>
+					<name>performRelease</name>
+					<value>true</value>
+				</property>
+			</activation>
 			<build>
 				<plugins>
 					<!-- use dokka-maven-plugin to generate javadoc for kotlin project -->
diff --git a/pom.xml b/pom.xml
index 22430b1..eb6bf49 100644
--- a/pom.xml
+++ b/pom.xml
@@ -341,12 +341,27 @@
 			<plugin>
 				<groupId>org.sonatype.plugins</groupId>
 				<artifactId>nexus-staging-maven-plugin</artifactId>
-				<version>1.6.8</version>
 				<extensions>true</extensions>
+				<!-- In multi-module builds using the deploy-at-end feature,
+					 the deployment of all components is performed in the last module based on the reactor order.
+					 If this property is set to true in the last module,
+					 all staging deployment for all modules will be skipped.
+					 so, we'll config nexus deploy after every moudle's deploy phase
+				-->
+				<!-- see: https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin#configuring-the-plugin -->
+				<executions>
+					<execution>
+						<id>default-deploy</id>
+						<phase>deploy</phase>
+						<goals>
+							<goal>deploy</goal>
+						</goals>
+					</execution>
+				</executions>
 				<configuration>
 					<serverId>ossrh</serverId>
 					<nexusUrl>https://s01.oss.sonatype.org/</nexusUrl>
-					<autoReleaseAfterClose>true</autoReleaseAfterClose>
+					<autoReleaseAfterClose>false</autoReleaseAfterClose>
 				</configuration>
 			</plugin>
 			<plugin>
@@ -432,6 +447,11 @@
 					<artifactId>git-commit-id-plugin</artifactId>
 					<version>4.9.10</version>
 				</plugin>
+				<plugin>
+					<groupId>org.sonatype.plugins</groupId>
+					<artifactId>nexus-staging-maven-plugin</artifactId>
+					<version>1.6.8</version>
+				</plugin>
 			</plugins>
 		</pluginManagement>
 	</build>