Procházet zdrojové kódy

发布到maven仓库

JustryDeng před 5 roky
rodič
revize
604098f9aa
1 změnil soubory, kde provedl 59 přidání a 11 odebrání
  1. 59 11
      pom.xml

+ 59 - 11
pom.xml

@@ -10,8 +10,12 @@
     <groupId>com.idea-aedi</groupId>
     <artifactId>class-winter</artifactId>
     <version>1.0.0</version>
+
+    <!-- 配置项目的基础信息 -->
     <name>class-winter</name>
-    <description>class混淆、加密</description>
+    <url>https://gitee.com/JustryDeng/class-winter</url>
+    <description>Obfuscate encryption .class file</description>
+
 
     <properties>
         <java.version>1.8</java.version>
@@ -47,15 +51,43 @@
     </developers>
 
     <distributionManagement>
+        <!-- 要发布到的snapshot仓库 -->
         <snapshotRepository>
-            <!-- id与settings.xml中的server id对应 -->
+            <!-- 通过此id定位maven配置文件settings.xml中配置的用户名密码,以登录指定的url -->
             <id>ossrh</id>
-            <url>https://oss.sonatype.org/content/repositories/snapshots</url>
+            <!--
+                特别注意: 其中地址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与settings.xml中的server id对应 -->
+            <!-- 通过此id定位maven配置文件settings.xml中配置的用户名密码,以登录指定的url -->
             <id>ossrh</id>
-            <url>https://oss.sonatype.org/service/local/staging/deploy/maven2/</url>
+            <!--
+                特别注意: 其中地址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>
 
@@ -82,7 +114,7 @@
                 <artifactId>maven-javadoc-plugin</artifactId>
                 <version>3.1.0</version>
                 <configuration>
-                    <!-- 解决报错 -->
+                    <!-- 解决(因javadoc写得不规范导致的)报错 -->
                     <additionalOptions>
                         <additionalOption>-Xdoclint:none</additionalOption>
                     </additionalOptions>
@@ -103,16 +135,29 @@
                 </executions>
             </plugin>
 
-            <!-- nexus流程处理插件 -->
+            <!-- nexus流程处理插件(deploy、release、close issue) -->
             <plugin>
                 <groupId>org.sonatype.plugins</groupId>
                 <artifactId>nexus-staging-maven-plugin</artifactId>
                 <version>1.6.7</version>
                 <extensions>true</extensions>
                 <configuration>
-                    <!-- 与settings.xml中的server id对应 -->
+                    <!-- 通过此id定位maven配置文件settings.xml中配置的用户名密码,以登录指定的url -->
                     <serverId>ossrh</serverId>
-                    <nexusUrl>https://oss.sonatype.org/</nexusUrl>
+                    <!--
+                        特别注意: 其中地址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>
@@ -150,8 +195,11 @@
                          -->
                         <configuration>
                             <executable>C:/Program Files (x86)/GnuPG/bin/gpg.exe</executable>
-                            <!-- 创建gpg密钥对时指定的密码(如果这里不指定的话, 那么需要用到的时候就会让你主动输入) -->
-                            <passphrase>dengshuai1994</passphrase>
+                            <!--
+                                指定GPG 代表公钥的密钥id
+                                注:因为我们可能拥有多个GPG密钥对,所以我们需要指定使用哪一个
+                            -->
+                            <passphrase>F4A9FB7A887DCB32F185DBEF3D8B00493FAFC7F9</passphrase>
                         </configuration>
                     </execution>
                 </executions>