chore(deploy): fix maven.deploy.skip problem for submodule again...

pom.xml

@@ -514,20 +514,35 @@
                 </executions>
             </plugin>
             <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.
-                -->
                 <groupId>org.sonatype.plugins</groupId>
                 <artifactId>nexus-staging-maven-plugin</artifactId>
                 <version>1.6.13</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 deploy phase of every module
+                    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://oss.sonatype.org/</nexusUrl>
                     <autoReleaseAfterClose>true</autoReleaseAfterClose>
-                    <!--
+                        <!--
+                        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