chore => maven发布信息更新

pom.xml

@@ -50,50 +50,8 @@
         </developer>
     </developers>
 
-    <distributionManagement>
-        <!-- 要发布到的snapshot仓库 -->
-        <snapshotRepository>
-            <!-- 通过此id定位maven配置文件settings.xml中配置的用户名密码，以登录指定的url -->
-            <id>ossrh</id>
-            <!--
-                特别注意: 其中地址s01.oss.sonatype.org是你在jira中提issue后，审核员告诉你的，
-                对应部分原文是:
-                com.idea-aedi has been prepared, now user(s) JustryDeng can:
-                Publish snapshot and release artifacts to s01.oss.sonatype.org
-                Have a look at this section of our official guide for deployment instructions:
-                https://central.sonatype.org/publish/publish-guide/#deployment
-
-                Please comment on this ticket when you've released your first component(s), so we can activate the sync to Maven Central.
-                Depending on your build configuration, this might happen automatically. If not, you can follow the steps in this section of our guide:
-                https://central.sonatype.org/publish/release/
-                可知，这个地址要根据它给的指引来填
-             -->
-            <url>https://s01.oss.sonatype.org/content/repositories/snapshots</url>
-        </snapshotRepository>
-        <!-- 要发布到的仓库 -->
-        <repository>
-            <!-- 通过此id定位maven配置文件settings.xml中配置的用户名密码，以登录指定的url -->
-            <id>ossrh</id>
-            <!--
-                特别注意: 其中地址s01.oss.sonatype.org是你在jira中提issue后，审核员告诉你的，
-                对应部分原文是:
-                com.idea-aedi has been prepared, now user(s) JustryDeng can:
-                Publish snapshot and release artifacts to s01.oss.sonatype.org
-                Have a look at this section of our official guide for deployment instructions:
-                https://central.sonatype.org/publish/publish-guide/#deployment
-
-                Please comment on this ticket when you've released your first component(s), so we can activate the sync to Maven Central.
-                Depending on your build configuration, this might happen automatically. If not, you can follow the steps in this section of our guide:
-                https://central.sonatype.org/publish/release/
-                可知，这个地址要根据它给的指引来填
-             -->
-            <url>https://s01.oss.sonatype.org/service/local/staging/deploy/maven2/</url>
-        </repository>
-    </distributionManagement>
-
     <build>
         <plugins>
-            <!-- 打包源码 -->
             <plugin>
                 <groupId>org.apache.maven.plugins</groupId>
                 <artifactId>maven-source-plugin</artifactId>
@@ -108,22 +66,14 @@
                 </executions>
             </plugin>
 
-            <!-- 打包javadoc -->
             <plugin>
                 <groupId>org.apache.maven.plugins</groupId>
                 <artifactId>maven-javadoc-plugin</artifactId>
-                <version>3.1.0</version>
+                <version>3.6.3</version>
                 <configuration>
-                    <!-- 解决(因javadoc写得不规范导致的)报错 -->
                     <additionalOptions>
                         <additionalOption>-Xdoclint:none</additionalOption>
                     </additionalOptions>
-                    <!--
-                    解决乱码:
-                       在IDEA中，打开File | Settings | Build, Execution, Deployment | Build Tools | Maven | Runner
-                       在VM Options中添加-Dfile.encoding=GBK，切记一定是GBK。即使用UTF-8的话，依然是乱码，这是因为Maven的
-                       默认平台编码是GBK（通过mvn -version可看见）。
-                     -->
                 </configuration>
                 <executions>
                     <execution>
@@ -135,47 +85,17 @@
                 </executions>
             </plugin>
 
-            <!-- nexus流程处理插件 实现自动（deploy、release...）发布等 -->
+            <!-- Maven Central官方的发布部署插件 -->
             <plugin>
-                <groupId>org.sonatype.plugins</groupId>
-                <artifactId>nexus-staging-maven-plugin</artifactId>
-                <version>1.6.7</version>
+                <groupId>org.sonatype.central</groupId>
+                <artifactId>central-publishing-maven-plugin</artifactId>
+                <version>0.8.0</version>
                 <extensions>true</extensions>
                 <configuration>
-                    <!-- 通过此id定位maven配置文件settings.xml中配置的用户名密码，以登录指定的url -->
-                    <serverId>ossrh</serverId>
-                    <!--
-                        特别注意: 其中地址s01.oss.sonatype.org是你在jira中提issue后，审核员告诉你的，
-                        对应部分原文是:
-                        com.idea-aedi has been prepared, now user(s) JustryDeng can:
-                        Publish snapshot and release artifacts to s01.oss.sonatype.org
-                        Have a look at this section of our official guide for deployment instructions:
-                        https://central.sonatype.org/publish/publish-guide/#deployment
-
-                        Please comment on this ticket when you've released your first component(s), so we can activate the sync to Maven Central.
-                        Depending on your build configuration, this might happen automatically. If not, you can follow the steps in this section of our guide:
-                        https://central.sonatype.org/publish/release/
-                        可知，这个地址要根据它给的指引来填
-                     -->
-                    <nexusUrl>https://s01.oss.sonatype.org/</nexusUrl>
-                    <autoReleaseAfterClose>true</autoReleaseAfterClose>
-                </configuration>
-            </plugin>
-
-            <!-- 发布到release仓库的部署插件 -->
-            <plugin>
-                <groupId>org.apache.maven.plugins</groupId>
-                <artifactId>maven-release-plugin</artifactId>
-                <version>2.5.3</version>
-                <configuration>
-                    <autoVersionSubmodules>true</autoVersionSubmodules>
-                    <useReleaseProfile>false</useReleaseProfile>
-                    <releaseProfiles>release</releaseProfiles>
-                    <goals>deploy</goals>
+                    <publishingServerId>central-sonatyp</publishingServerId>
                 </configuration>
             </plugin>
 
-            <!-- gpg签名认证 -->
             <plugin>
                 <groupId>org.apache.maven.plugins</groupId>
                 <artifactId>maven-gpg-plugin</artifactId>
@@ -187,18 +107,8 @@
                         <goals>
                             <goal>sign</goal>
                         </goals>
-                        <!--
-                            注: 如果不主动指定gpg.exe的话，那么可能(因为和idea内部发生了未知冲突)报错
-                            Cannot run program "gpg.exe": CreateProcess error=2, 系统找不到指定的文件。
-                            注: 当然，如果你直接用的git bash之类的工具执行mvn，而不是用idea提供的maven功能
-                                的话，你也可以不指定executable。
-                         -->
                         <configuration>
                             <executable>C:/Program Files (x86)/GnuPG/bin/gpg.exe</executable>
-                            <!--
-                                指定GPG 代表公钥的密钥id
-                                注:因为我们可能拥有多个GPG密钥对，所以我们需要指定使用哪一个
-                            -->
                             <passphrase>F4A9FB7A887DCB32F185DBEF3D8B00493FAFC7F9</passphrase>
                         </configuration>
                     </execution>