From e5cde1b30ec95d08f04ac47b630729657ba737f9 Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Fri, 10 Jul 2026 03:07:52 -0700
Subject: [PATCH 01/19] fix:Checkstyle check

---
 .github/workflows/checkstyle.yml | 33 +++++++++++++++++++-------------
 pom.xml                          | 23 ++++++++++++++++++++++
 2 files changed, 43 insertions(+), 13 deletions(-)

diff --git a/.github/workflows/checkstyle.yml b/.github/workflows/checkstyle.yml
index 74529b84..3d0c1283 100644
--- a/.github/workflows/checkstyle.yml
+++ b/.github/workflows/checkstyle.yml
@@ -3,35 +3,42 @@ name: Checkstyle Code Quality
 on:
   push:
     branches:
-      - develop  # 或者你想要检查的分支
+      - develop
   pull_request:
     branches:
-      - develop  # 你可以在 PR 时检查代码
+      - develop
 
 jobs:
-  check:
+  checkstyle:
     runs-on: ubuntu-24.04
 
     steps:
-      # 检出代码
       - name: Checkout code
         uses: actions/checkout@v4
 
-      # 设置 JDK（如果是 Java 项目）
-      - name: Set up JDK 17.*
+      - name: Set up JDK 17
         uses: actions/setup-java@v4
         with:
-          java-version: '17.*'
+          java-version: '17'
           distribution: 'temurin'
 
-      # 安装依赖并运行 Checkstyle（如果是 Maven 项目）
-      - name: Install dependencies and run Checkstyle
-        run: |
-          mvn clean package
+      # 缓存 Maven 依赖，加速构建
+      - name: Cache Maven dependencies
+        uses: actions/cache@v4
+        with:
+          path: ~/.m2/repository
+          key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
+          restore-keys: |
+            ${{ runner.os }}-maven-
+
+      # 直接运行 Checkstyle 检查（不执行完整的 package）
+      - name: Run Checkstyle
+        run: mvn checkstyle:check
 
-      # 查看 Checkstyle 检查报告
+      # 如果检查失败，仍然上传报告供查看
       - name: Upload Checkstyle report
+        if: always()  # 即使失败也上传报告
         uses: actions/upload-artifact@v4
         with:
           name: checkstyle-report
-          path: target/checkstyle-result.xml  # 这个路径应该是 Maven 生成的检查报告路径
+          path: target/checkstyle-result.xml
diff --git a/pom.xml b/pom.xml
index c651a73c..1734cb4a 100644
--- a/pom.xml
+++ b/pom.xml
@@ -235,6 +235,29 @@
                     <target>17</target>   <!-- 生成字节码的 Java 版本 -->
                 </configuration>
             </plugin>
+
+            <plugin>
+                <groupId>org.apache.maven.plugins</groupId>
+                <artifactId>maven-checkstyle-plugin</artifactId>
+                <version>3.3.1</version>
+                <configuration>
+                    <!-- 指定华为Java编码规范的配置文件 -->
+                    <configLocation>settings/checkstyle.xml</configLocation>
+                    <!-- 检查失败时构建失败（阻止CI通过） -->
+                    <failOnViolation>true</failOnViolation>
+                    <!-- 输出格式 -->
+                    <outputFileFormat>xml</outputFileFormat>
+                </configuration>
+                <executions>
+                    <execution>
+                        <id>checkstyle-check</id>
+                        <phase>validate</phase>  <!-- 或 verify，在早期阶段就执行 -->
+                        <goals>
+                            <goal>check</goal>
+                        </goals>
+                    </execution>
+                </executions>
+            </plugin>
         </plugins>
     </build>
 </project>

From 95b5fb32fb6366fe99dbbe30d8253ea417a3b33a Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Fri, 10 Jul 2026 03:40:24 -0700
Subject: [PATCH 02/19] fix:Checkstyle check

---
 codestyle/huawei-codestyle.xml | 287 +++++++++++++++++++++++++++++++++
 pom.xml                        |   2 +-
 2 files changed, 288 insertions(+), 1 deletion(-)
 create mode 100644 codestyle/huawei-codestyle.xml

diff --git a/codestyle/huawei-codestyle.xml b/codestyle/huawei-codestyle.xml
new file mode 100644
index 00000000..e7ab75b1
--- /dev/null
+++ b/codestyle/huawei-codestyle.xml
@@ -0,0 +1,287 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE module PUBLIC "-//Puppy Crawl//DTD Check Configuration 1.2//EN" "http://www.puppycrawl.com/dtds/configuration_1_2.dtd">
+
+<!-- Generated by RHY @will_awoke -->
+
+<module name="Checker">
+
+  <property name="charset" value="UTF-8"/>
+  <property name="severity" value="warning"/>
+
+  <!-- Checks for Size Violations.  -->
+  <!-- 检查文件的长度（行） default max=2000 -->
+  <module name="FileLength">
+    <property name="max" value="2500"/>
+  </module>
+
+  <!-- Checks that property files contain the same keys. -->
+  <!-- 检查**.properties配置文件 是否有相同的key
+  <module name="Translation">
+  </module>
+  -->
+
+  <module name="TreeWalker">
+
+    <!-- Checks for imports    -->
+    <!-- 必须导入类的完整路径，即不能使用*导入所需的类 -->
+    <module name="AvoidStarImport"/>
+
+    <!-- 检查是否从非法的包中导入了类 illegalPkgs: 定义非法的包名称-->
+    <module name="IllegalImport"/> <!-- defaults to sun.* packages -->
+
+    <!-- 检查是否导入了不必显示导入的类-->
+    <module name="RedundantImport"/>
+
+    <!-- 检查是否导入的包没有使用-->
+    <module name="UnusedImports"/>
+
+    <!-- Checks for whitespace
+    <module name="EmptyForIteratorPad"/>
+    <module name="MethodParamPad"/>
+    <module name="NoWhitespaceAfter"/>
+    <module name="NoWhitespaceBefore"/>
+    <module name="OperatorWrap"/>
+    <module name="ParenPad"/>
+    <module name="TypecastParenPad"/>
+    <module name="WhitespaceAfter"/>
+    <module name="WhitespaceAround"/>
+    -->
+
+    <!-- 检查类和接口的javadoc 默认不检查author 和version tags
+      authorFormat: 检查author标签的格式
+			versionFormat: 检查version标签的格式
+			scope: 可以检查的类的范围，例如：public只能检查public修饰的类，private可以检查所有的类
+			excludeScope: 不能检查的类的范围，例如：public，public的类将不被检查，但访问权限小于public的类仍然会检查，其他的权限以此类推
+			tokens: 该属性适用的类型，例如：CLASS_DEF,INTERFACE_DEF -->
+    <module name="JavadocType">
+      <property name="authorFormat" value="\S"/>
+      <property name="scope" value="protected"/>
+      <property name="tokens" value="CLASS_DEF,INTERFACE_DEF"/>
+    </module>
+
+    <!-- 检查方法的javadoc的注释
+			scope: 可以检查的方法的范围，例如：public只能检查public修饰的方法，private可以检查所有的方法
+			allowMissingParamTags: 是否忽略对参数注释的检查
+			allowMissingThrowsTags: 是否忽略对throws注释的检查
+			allowMissingReturnTag: 是否忽略对return注释的检查 -->
+    <module name="JavadocMethod">
+      <property name="scope" value="private"/>
+      <property name="allowMissingParamTags" value="false"/>
+      <property name="allowMissingThrowsTags" value="false"/>
+      <property name="allowMissingReturnTag" value="false"/>
+      <property name="tokens" value="METHOD_DEF"/>
+      <property name="allowUndeclaredRTE" value="true"/>
+      <property name="allowThrowsTagsForSubclasses" value="true"/>
+      <!--允许get set 方法没有注释-->
+      <property name="allowMissingPropertyJavadoc" value="true"/>
+    </module>
+
+    <!-- 检查类变量的注释
+			scope: 检查变量的范围，例如：public只能检查public修饰的变量，private可以检查所有的变量 -->
+    <module name="JavadocVariable">
+      <property name="scope" value="private"/>
+    </module>
+
+    <!--option: 定义左大括号'{'显示位置，eol在同一行显示，nl在下一行显示
+      maxLineLength: 大括号'{'所在行行最多容纳的字符数
+      tokens: 该属性适用的类型，例：CLASS_DEF,INTERFACE_DEF,METHOD_DEF,CTOR_DEF -->
+    <module name="LeftCurly">
+      <property name="option" value="nl"/>
+    </module>
+
+    <!-- NeedBraces 检查是否应该使用括号的地方没有加括号
+      tokens: 定义检查的类型 -->
+    <module name="NeedBraces"/>
+
+    <!-- Checks the placement of right curly braces ('}') for  else, try, and catch tokens. The policy to verify is specified using property  option.
+      option: 右大括号是否单独一行显示
+      tokens: 定义检查的类型  -->
+    <module name="RightCurly">
+      <property name="option" value="alone"/>
+    </module>
+
+    <!-- 检查在重写了equals方法后是否重写了hashCode方法 -->
+    <module name="EqualsHashCode"/>
+
+    <!--  Checks for illegal instantiations where a factory method is preferred.
+      Rationale: Depending on the project, for some classes it might be preferable to create instances through factory methods rather than calling the constructor.
+      A simple example is the java.lang.Boolean class. In order to save memory and CPU cycles, it is preferable to use the predefined constants TRUE and FALSE. Constructor invocations should be replaced by calls to Boolean.valueOf().
+      Some extremely performance sensitive projects may require the use of factory methods for other classes as well, to enforce the usage of number caches or object pools. -->
+    <module name="IllegalInstantiation">
+      <property name="classes" value="java.lang.Boolean"/>
+    </module>
+
+    <!-- Checks for Naming Conventions.   命名规范   -->
+    <!-- local, final variables, including catch parameters -->
+    <module name="LocalFinalVariableName"/>
+
+    <!-- local, non-final variables, including catch parameters-->
+    <module name="LocalVariableName"/>
+
+    <!-- static, non-final fields -->
+    <module name="StaticVariableName">
+      <property name="format" value="(^[A-Z0-9_]{0,19}$)"/>
+    </module>
+
+    <!-- packages -->
+    <module name="PackageName" >
+      <property name="format" value="^[a-z]+(\.[a-z][a-z0-9]*)*$"/>
+    </module>
+
+    <!-- classes and interfaces -->
+    <module name="TypeName">
+      <property name="format" value="(^[A-Z][a-zA-Z0-9]{0,19}$)"/>
+    </module>
+
+    <!-- methods -->
+    <module name="MethodName">
+      <property name="format" value="(^[a-z][a-zA-Z0-9]{0,19}$)"/>
+    </module>
+
+    <!-- non-static fields -->
+    <module name="MemberName">
+      <property name="format" value="(^[a-z][a-z0-9][a-zA-Z0-9]{0,19}$)"/>
+    </module>
+
+    <!-- parameters -->
+    <module name="ParameterName">
+      <property name="format" value="(^[a-z][a-zA-Z0-9_]{0,19}$)"/>
+    </module>
+
+    <!-- constants (static,  final fields) -->
+    <module name="ConstantName">
+      <property name="format" value="(^[A-Z0-9_]{0,19}$)"/>
+    </module>
+
+    <!-- 代码缩进   -->
+    <module name="Indentation">
+    </module>
+
+    <!-- Checks for redundant exceptions declared in throws clause such as duplicates, unchecked exceptions or subclasses of another declared exception.
+      检查是否抛出了多余的异常
+    <module name="RedundantThrows">
+    	<property name="logLoadErrors" value="true"/>
+    	<property name="suppressLoadErrors" value="true"/>
+    </module>
+    -->
+
+    <!--  Checks for overly complicated boolean expressions. Currently finds code like  if (b == true), b || true, !false, etc.
+      检查boolean值是否冗余的地方
+      Rationale: Complex boolean logic makes code hard to understand and maintain. -->
+    <module name="SimplifyBooleanExpression"/>
+
+    <!--  Checks for overly complicated boolean return statements. For example the following code
+       检查是否存在过度复杂的boolean返回值
+       if (valid())
+          return false;
+       else
+          return true;
+       could be written as
+          return !valid();
+       The Idea for this Check has been shamelessly stolen from the equivalent PMD rule. -->
+    <module name="SimplifyBooleanReturn"/>
+
+    <!-- Checks that a class which has only private constructors is declared as final.只有私有构造器的类必须声明为final-->
+    <module name="FinalClass"/>
+
+    <!--  Make sure that utility classes (classes that contain only static methods or fields in their API) do not have a public constructor.
+      确保Utils类（只提供static方法和属性的类）没有public构造器。
+      Rationale: Instantiating utility classes does not make sense. Hence the constructors should either be private or (if you want to allow subclassing) protected. A common mistake is forgetting to hide the default constructor.
+      If you make the constructor protected you may want to consider the following constructor implementation technique to disallow instantiating subclasses:
+      public class StringUtils // not final to allow subclassing
+      {
+          protected StringUtils() {
+              throw new UnsupportedOperationException(); // prevents calls from subclass
+          }
+          public static int count(char c, String s) {
+              // ...
+          }
+      }
+   <module name="HideUtilityClassConstructor"/>
+   -->
+
+    <!--  Checks visibility of class members. Only static final members may be public; other class members must be private unless property protectedAllowed or packageAllowed is set.
+      检查class成员属性可见性。只有static final 修饰的成员是可以public的。其他的成员属性必需是private的，除非属性protectedAllowed或者packageAllowed设置了true.
+       Public members are not flagged if the name matches the public member regular expression (contains "^serialVersionUID$" by default). Note: Checkstyle 2 used to include "^f[A-Z][a-zA-Z0-9]*$" in the default pattern to allow CMP for EJB 1.1 with the default settings. With EJB 2.0 it is not longer necessary to have public access for persistent fields, hence the default has been changed.
+       Rationale: Enforce encapsulation. 强制封装 -->
+    <module name="VisibilityModifier"/>
+
+    <!-- 每一行只能定义一个变量 -->
+    <module name="MultipleVariableDeclarations">
+    </module>
+
+    <!-- Checks the style of array type definitions. Some like Java-style: public static void main(String[] args) and some like C-style: public static void main(String args[])
+      检查再定义数组时，采用java风格还是c风格，例如：int[] num是java风格，int num[]是c风格。默认是java风格-->
+    <module name="ArrayTypeStyle">
+    </module>
+
+    <!-- Checks that there are no "magic numbers", where a magic number is a numeric literal that is not defined as a constant. By default, -1, 0, 1, and 2 are not considered to be magic numbers.
+    <module name="MagicNumber">
+    </module>
+    -->
+
+    <!-- A check for TODO: comments. Actually it is a generic regular expression matcher on Java comments. To check for other patterns in Java comments, set property format.
+       检查是否存在TODO（待处理） TODO是javaIDE自动生成的。一般代码写完后要去掉。
+     -->
+    <module name="TodoComment"/>
+
+    <!--  Checks that long constants are defined with an upper ell. That is ' L' and not 'l'. This is in accordance to the Java Language Specification,  Section 3.10.1.
+      检查是否在long类型是否定义了大写的L.字母小写l和数字1（一）很相似。
+      looks a lot like 1. -->
+    <module name="UpperEll"/>
+
+    <!--  Checks that switch statement has "default" clause. 检查switch语句是否有‘default’从句
+       Rationale: It's usually a good idea to introduce a default case in every switch statement.
+       Even if the developer is sure that all currently possible cases are covered, this should be expressed in the default branch,
+        e.g. by using an assertion. This way the code is protected aginst later changes, e.g. introduction of new types in an enumeration type. -->
+    <module name="MissingSwitchDefault"/>
+
+    <!--检查switch中case后是否加入了跳出语句，例如：return、break、throw、continue -->
+    <module name="FallThrough"/>
+
+    <!-- Checks the number of parameters of a method or constructor. max default 7个. -->
+    <module name="ParameterNumber">
+      <property name="max" value="5"/>
+    </module>
+
+    <!-- 每行字符数 -->
+    <module name="LineLength">
+      <property name="max" value="200"/>
+    </module>
+
+    <!-- Checks for long methods and constructors. max default 150行. max=300 设置长度300 -->
+    <module name="MethodLength">
+      <property name="max" value="300"/>
+    </module>
+
+    <!-- ModifierOrder 检查修饰符的顺序，默认是 public,protected,private,abstract,static,final,transient,volatile,synchronized,native -->
+    <module name="ModifierOrder">
+    </module>
+
+    <!-- 检查是否有多余的修饰符，例如：接口中的方法不必使用public、abstract修饰  -->
+    <module name="RedundantModifier">
+    </module>
+
+    <!--- 字符串比较必须使用 equals() -->
+    <module name="StringLiteralEquality">
+    </module>
+
+    <!-- if-else嵌套语句个数 最多4层 -->
+    <module name="NestedIfDepth">
+      <property name="max" value="3"/>
+    </module>
+
+    <!-- try-catch 嵌套语句个数 最多2层 -->
+    <module name="NestedTryDepth">
+      <property name="max" value="2"/>
+    </module>
+
+    <!-- 返回个数 -->
+    <module name="ReturnCount">
+      <property name="max" value="5"/>
+      <property name="format" value="^$"/>
+    </module>
+
+  </module>
+
+</module>
\ No newline at end of file
diff --git a/pom.xml b/pom.xml
index 1734cb4a..c1390dc5 100644
--- a/pom.xml
+++ b/pom.xml
@@ -242,7 +242,7 @@
                 <version>3.3.1</version>
                 <configuration>
                     <!-- 指定华为Java编码规范的配置文件 -->
-                    <configLocation>settings/checkstyle.xml</configLocation>
+                    <configLocation>checkstyle/huawei-checkstyle.xml</configLocation>
                     <!-- 检查失败时构建失败（阻止CI通过） -->
                     <failOnViolation>true</failOnViolation>
                     <!-- 输出格式 -->

From e48f78a49f00a7828d1cdb0f02aae5af5a6b16ed Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Fri, 10 Jul 2026 03:47:05 -0700
Subject: [PATCH 03/19] fix:Checkstyle check

---
 .../huawei-codestyle.xml => checkstyle/huawei-checkstyle.xml      | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename codestyle/huawei-codestyle.xml => checkstyle/huawei-checkstyle.xml (100%)

diff --git a/codestyle/huawei-codestyle.xml b/checkstyle/huawei-checkstyle.xml
similarity index 100%
rename from codestyle/huawei-codestyle.xml
rename to checkstyle/huawei-checkstyle.xml

From f7978bed20592583edf9930d85ae17a87d0ddfcb Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Fri, 10 Jul 2026 03:58:14 -0700
Subject: [PATCH 04/19] fix:Checkstyle check

---
 pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pom.xml b/pom.xml
index c1390dc5..b7ddff00 100644
--- a/pom.xml
+++ b/pom.xml
@@ -242,7 +242,7 @@
                 <version>3.3.1</version>
                 <configuration>
                     <!-- 指定华为Java编码规范的配置文件 -->
-                    <configLocation>checkstyle/huawei-checkstyle.xml</configLocation>
+                    <configLocation>${project.basedir}/checkstyle/huawei-checkstyle.xml</configLocation>
                     <!-- 检查失败时构建失败（阻止CI通过） -->
                     <failOnViolation>true</failOnViolation>
                     <!-- 输出格式 -->

From 426994319c253f635d9b309aa8f9f23fa67c0e61 Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Fri, 10 Jul 2026 04:03:53 -0700
Subject: [PATCH 05/19] fix:Checkstyle check

---
 checkstyle/huawei-checkstyle.xml | 11 -----------
 1 file changed, 11 deletions(-)

diff --git a/checkstyle/huawei-checkstyle.xml b/checkstyle/huawei-checkstyle.xml
index e7ab75b1..0d68712a 100644
--- a/checkstyle/huawei-checkstyle.xml
+++ b/checkstyle/huawei-checkstyle.xml
@@ -35,17 +35,6 @@
     <!-- 检查是否导入的包没有使用-->
     <module name="UnusedImports"/>
 
-    <!-- Checks for whitespace
-    <module name="EmptyForIteratorPad"/>
-    <module name="MethodParamPad"/>
-    <module name="NoWhitespaceAfter"/>
-    <module name="NoWhitespaceBefore"/>
-    <module name="OperatorWrap"/>
-    <module name="ParenPad"/>
-    <module name="TypecastParenPad"/>
-    <module name="WhitespaceAfter"/>
-    <module name="WhitespaceAround"/>
-    -->
 
     <!-- 检查类和接口的javadoc 默认不检查author 和version tags
       authorFormat: 检查author标签的格式

From d3fd7b7f237c987db676d6824fb5215c4096fcab Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Fri, 10 Jul 2026 04:14:47 -0700
Subject: [PATCH 06/19] fix:Checkstyle check

---
 checkstyle/huawei-checkstyle.xml | 2 +-
 pom.xml                          | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/checkstyle/huawei-checkstyle.xml b/checkstyle/huawei-checkstyle.xml
index 0d68712a..d3d44b62 100644
--- a/checkstyle/huawei-checkstyle.xml
+++ b/checkstyle/huawei-checkstyle.xml
@@ -6,7 +6,7 @@
 <module name="Checker">
 
   <property name="charset" value="UTF-8"/>
-  <property name="severity" value="warning"/>
+  <property name="severity" value="error"/>
 
   <!-- Checks for Size Violations.  -->
   <!-- 检查文件的长度（行） default max=2000 -->
diff --git a/pom.xml b/pom.xml
index b7ddff00..fc00b947 100644
--- a/pom.xml
+++ b/pom.xml
@@ -245,6 +245,7 @@
                     <configLocation>${project.basedir}/checkstyle/huawei-checkstyle.xml</configLocation>
                     <!-- 检查失败时构建失败（阻止CI通过） -->
                     <failOnViolation>true</failOnViolation>
+                    <violationSeverity>warning</violationSeverity>
                     <!-- 输出格式 -->
                     <outputFileFormat>xml</outputFileFormat>
                 </configuration>

From b58e79f265ccd7dad82484b34e9b302d28cb8661 Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Fri, 10 Jul 2026 04:15:40 -0700
Subject: [PATCH 07/19] fix:Checkstyle check

---
 pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pom.xml b/pom.xml
index fc00b947..6358bacb 100644
--- a/pom.xml
+++ b/pom.xml
@@ -242,7 +242,7 @@
                 <version>3.3.1</version>
                 <configuration>
                     <!-- 指定华为Java编码规范的配置文件 -->
-                    <configLocation>${project.basedir}/checkstyle/huawei-checkstyle.xml</configLocation>
+                    <configLocation>./checkstyle/huawei-checkstyle.xml</configLocation>
                     <!-- 检查失败时构建失败（阻止CI通过） -->
                     <failOnViolation>true</failOnViolation>
                     <violationSeverity>warning</violationSeverity>

From 45714f7e8fb698aa2307a97ce09006bbac6e539e Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Fri, 10 Jul 2026 04:19:53 -0700
Subject: [PATCH 08/19] fix:Checkstyle check

---
 checkstyle/huawei-checkstyle.xml | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/checkstyle/huawei-checkstyle.xml b/checkstyle/huawei-checkstyle.xml
index d3d44b62..2512af0c 100644
--- a/checkstyle/huawei-checkstyle.xml
+++ b/checkstyle/huawei-checkstyle.xml
@@ -61,8 +61,7 @@
       <property name="tokens" value="METHOD_DEF"/>
       <property name="allowUndeclaredRTE" value="true"/>
       <property name="allowThrowsTagsForSubclasses" value="true"/>
-      <!--允许get set 方法没有注释-->
-      <property name="allowMissingPropertyJavadoc" value="true"/>
+
     </module>
 
     <!-- 检查类变量的注释

From 051cdc9f3c07b6a1aceddf5602216cb3c843373d Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Fri, 10 Jul 2026 04:27:20 -0700
Subject: [PATCH 09/19] fix:Checkstyle check

---
 checkstyle/huawei-checkstyle.xml | 306 ++++---------------------------
 1 file changed, 31 insertions(+), 275 deletions(-)

diff --git a/checkstyle/huawei-checkstyle.xml b/checkstyle/huawei-checkstyle.xml
index 2512af0c..c97cd6fd 100644
--- a/checkstyle/huawei-checkstyle.xml
+++ b/checkstyle/huawei-checkstyle.xml
@@ -1,275 +1,31 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE module PUBLIC "-//Puppy Crawl//DTD Check Configuration 1.2//EN" "http://www.puppycrawl.com/dtds/configuration_1_2.dtd">
-
-<!-- Generated by RHY @will_awoke -->
-
-<module name="Checker">
-
-  <property name="charset" value="UTF-8"/>
-  <property name="severity" value="error"/>
-
-  <!-- Checks for Size Violations.  -->
-  <!-- 检查文件的长度（行） default max=2000 -->
-  <module name="FileLength">
-    <property name="max" value="2500"/>
-  </module>
-
-  <!-- Checks that property files contain the same keys. -->
-  <!-- 检查**.properties配置文件 是否有相同的key
-  <module name="Translation">
-  </module>
-  -->
-
-  <module name="TreeWalker">
-
-    <!-- Checks for imports    -->
-    <!-- 必须导入类的完整路径，即不能使用*导入所需的类 -->
-    <module name="AvoidStarImport"/>
-
-    <!-- 检查是否从非法的包中导入了类 illegalPkgs: 定义非法的包名称-->
-    <module name="IllegalImport"/> <!-- defaults to sun.* packages -->
-
-    <!-- 检查是否导入了不必显示导入的类-->
-    <module name="RedundantImport"/>
-
-    <!-- 检查是否导入的包没有使用-->
-    <module name="UnusedImports"/>
-
-
-    <!-- 检查类和接口的javadoc 默认不检查author 和version tags
-      authorFormat: 检查author标签的格式
-			versionFormat: 检查version标签的格式
-			scope: 可以检查的类的范围，例如：public只能检查public修饰的类，private可以检查所有的类
-			excludeScope: 不能检查的类的范围，例如：public，public的类将不被检查，但访问权限小于public的类仍然会检查，其他的权限以此类推
-			tokens: 该属性适用的类型，例如：CLASS_DEF,INTERFACE_DEF -->
-    <module name="JavadocType">
-      <property name="authorFormat" value="\S"/>
-      <property name="scope" value="protected"/>
-      <property name="tokens" value="CLASS_DEF,INTERFACE_DEF"/>
-    </module>
-
-    <!-- 检查方法的javadoc的注释
-			scope: 可以检查的方法的范围，例如：public只能检查public修饰的方法，private可以检查所有的方法
-			allowMissingParamTags: 是否忽略对参数注释的检查
-			allowMissingThrowsTags: 是否忽略对throws注释的检查
-			allowMissingReturnTag: 是否忽略对return注释的检查 -->
-    <module name="JavadocMethod">
-      <property name="scope" value="private"/>
-      <property name="allowMissingParamTags" value="false"/>
-      <property name="allowMissingThrowsTags" value="false"/>
-      <property name="allowMissingReturnTag" value="false"/>
-      <property name="tokens" value="METHOD_DEF"/>
-      <property name="allowUndeclaredRTE" value="true"/>
-      <property name="allowThrowsTagsForSubclasses" value="true"/>
-
-    </module>
-
-    <!-- 检查类变量的注释
-			scope: 检查变量的范围，例如：public只能检查public修饰的变量，private可以检查所有的变量 -->
-    <module name="JavadocVariable">
-      <property name="scope" value="private"/>
-    </module>
-
-    <!--option: 定义左大括号'{'显示位置，eol在同一行显示，nl在下一行显示
-      maxLineLength: 大括号'{'所在行行最多容纳的字符数
-      tokens: 该属性适用的类型，例：CLASS_DEF,INTERFACE_DEF,METHOD_DEF,CTOR_DEF -->
-    <module name="LeftCurly">
-      <property name="option" value="nl"/>
-    </module>
-
-    <!-- NeedBraces 检查是否应该使用括号的地方没有加括号
-      tokens: 定义检查的类型 -->
-    <module name="NeedBraces"/>
-
-    <!-- Checks the placement of right curly braces ('}') for  else, try, and catch tokens. The policy to verify is specified using property  option.
-      option: 右大括号是否单独一行显示
-      tokens: 定义检查的类型  -->
-    <module name="RightCurly">
-      <property name="option" value="alone"/>
-    </module>
-
-    <!-- 检查在重写了equals方法后是否重写了hashCode方法 -->
-    <module name="EqualsHashCode"/>
-
-    <!--  Checks for illegal instantiations where a factory method is preferred.
-      Rationale: Depending on the project, for some classes it might be preferable to create instances through factory methods rather than calling the constructor.
-      A simple example is the java.lang.Boolean class. In order to save memory and CPU cycles, it is preferable to use the predefined constants TRUE and FALSE. Constructor invocations should be replaced by calls to Boolean.valueOf().
-      Some extremely performance sensitive projects may require the use of factory methods for other classes as well, to enforce the usage of number caches or object pools. -->
-    <module name="IllegalInstantiation">
-      <property name="classes" value="java.lang.Boolean"/>
-    </module>
-
-    <!-- Checks for Naming Conventions.   命名规范   -->
-    <!-- local, final variables, including catch parameters -->
-    <module name="LocalFinalVariableName"/>
-
-    <!-- local, non-final variables, including catch parameters-->
-    <module name="LocalVariableName"/>
-
-    <!-- static, non-final fields -->
-    <module name="StaticVariableName">
-      <property name="format" value="(^[A-Z0-9_]{0,19}$)"/>
-    </module>
-
-    <!-- packages -->
-    <module name="PackageName" >
-      <property name="format" value="^[a-z]+(\.[a-z][a-z0-9]*)*$"/>
-    </module>
-
-    <!-- classes and interfaces -->
-    <module name="TypeName">
-      <property name="format" value="(^[A-Z][a-zA-Z0-9]{0,19}$)"/>
-    </module>
-
-    <!-- methods -->
-    <module name="MethodName">
-      <property name="format" value="(^[a-z][a-zA-Z0-9]{0,19}$)"/>
-    </module>
-
-    <!-- non-static fields -->
-    <module name="MemberName">
-      <property name="format" value="(^[a-z][a-z0-9][a-zA-Z0-9]{0,19}$)"/>
-    </module>
-
-    <!-- parameters -->
-    <module name="ParameterName">
-      <property name="format" value="(^[a-z][a-zA-Z0-9_]{0,19}$)"/>
-    </module>
-
-    <!-- constants (static,  final fields) -->
-    <module name="ConstantName">
-      <property name="format" value="(^[A-Z0-9_]{0,19}$)"/>
-    </module>
-
-    <!-- 代码缩进   -->
-    <module name="Indentation">
-    </module>
-
-    <!-- Checks for redundant exceptions declared in throws clause such as duplicates, unchecked exceptions or subclasses of another declared exception.
-      检查是否抛出了多余的异常
-    <module name="RedundantThrows">
-    	<property name="logLoadErrors" value="true"/>
-    	<property name="suppressLoadErrors" value="true"/>
-    </module>
-    -->
-
-    <!--  Checks for overly complicated boolean expressions. Currently finds code like  if (b == true), b || true, !false, etc.
-      检查boolean值是否冗余的地方
-      Rationale: Complex boolean logic makes code hard to understand and maintain. -->
-    <module name="SimplifyBooleanExpression"/>
-
-    <!--  Checks for overly complicated boolean return statements. For example the following code
-       检查是否存在过度复杂的boolean返回值
-       if (valid())
-          return false;
-       else
-          return true;
-       could be written as
-          return !valid();
-       The Idea for this Check has been shamelessly stolen from the equivalent PMD rule. -->
-    <module name="SimplifyBooleanReturn"/>
-
-    <!-- Checks that a class which has only private constructors is declared as final.只有私有构造器的类必须声明为final-->
-    <module name="FinalClass"/>
-
-    <!--  Make sure that utility classes (classes that contain only static methods or fields in their API) do not have a public constructor.
-      确保Utils类（只提供static方法和属性的类）没有public构造器。
-      Rationale: Instantiating utility classes does not make sense. Hence the constructors should either be private or (if you want to allow subclassing) protected. A common mistake is forgetting to hide the default constructor.
-      If you make the constructor protected you may want to consider the following constructor implementation technique to disallow instantiating subclasses:
-      public class StringUtils // not final to allow subclassing
-      {
-          protected StringUtils() {
-              throw new UnsupportedOperationException(); // prevents calls from subclass
-          }
-          public static int count(char c, String s) {
-              // ...
-          }
-      }
-   <module name="HideUtilityClassConstructor"/>
-   -->
-
-    <!--  Checks visibility of class members. Only static final members may be public; other class members must be private unless property protectedAllowed or packageAllowed is set.
-      检查class成员属性可见性。只有static final 修饰的成员是可以public的。其他的成员属性必需是private的，除非属性protectedAllowed或者packageAllowed设置了true.
-       Public members are not flagged if the name matches the public member regular expression (contains "^serialVersionUID$" by default). Note: Checkstyle 2 used to include "^f[A-Z][a-zA-Z0-9]*$" in the default pattern to allow CMP for EJB 1.1 with the default settings. With EJB 2.0 it is not longer necessary to have public access for persistent fields, hence the default has been changed.
-       Rationale: Enforce encapsulation. 强制封装 -->
-    <module name="VisibilityModifier"/>
-
-    <!-- 每一行只能定义一个变量 -->
-    <module name="MultipleVariableDeclarations">
-    </module>
-
-    <!-- Checks the style of array type definitions. Some like Java-style: public static void main(String[] args) and some like C-style: public static void main(String args[])
-      检查再定义数组时，采用java风格还是c风格，例如：int[] num是java风格，int num[]是c风格。默认是java风格-->
-    <module name="ArrayTypeStyle">
-    </module>
-
-    <!-- Checks that there are no "magic numbers", where a magic number is a numeric literal that is not defined as a constant. By default, -1, 0, 1, and 2 are not considered to be magic numbers.
-    <module name="MagicNumber">
-    </module>
-    -->
-
-    <!-- A check for TODO: comments. Actually it is a generic regular expression matcher on Java comments. To check for other patterns in Java comments, set property format.
-       检查是否存在TODO（待处理） TODO是javaIDE自动生成的。一般代码写完后要去掉。
-     -->
-    <module name="TodoComment"/>
-
-    <!--  Checks that long constants are defined with an upper ell. That is ' L' and not 'l'. This is in accordance to the Java Language Specification,  Section 3.10.1.
-      检查是否在long类型是否定义了大写的L.字母小写l和数字1（一）很相似。
-      looks a lot like 1. -->
-    <module name="UpperEll"/>
-
-    <!--  Checks that switch statement has "default" clause. 检查switch语句是否有‘default’从句
-       Rationale: It's usually a good idea to introduce a default case in every switch statement.
-       Even if the developer is sure that all currently possible cases are covered, this should be expressed in the default branch,
-        e.g. by using an assertion. This way the code is protected aginst later changes, e.g. introduction of new types in an enumeration type. -->
-    <module name="MissingSwitchDefault"/>
-
-    <!--检查switch中case后是否加入了跳出语句，例如：return、break、throw、continue -->
-    <module name="FallThrough"/>
-
-    <!-- Checks the number of parameters of a method or constructor. max default 7个. -->
-    <module name="ParameterNumber">
-      <property name="max" value="5"/>
-    </module>
-
-    <!-- 每行字符数 -->
-    <module name="LineLength">
-      <property name="max" value="200"/>
-    </module>
-
-    <!-- Checks for long methods and constructors. max default 150行. max=300 设置长度300 -->
-    <module name="MethodLength">
-      <property name="max" value="300"/>
-    </module>
-
-    <!-- ModifierOrder 检查修饰符的顺序，默认是 public,protected,private,abstract,static,final,transient,volatile,synchronized,native -->
-    <module name="ModifierOrder">
-    </module>
-
-    <!-- 检查是否有多余的修饰符，例如：接口中的方法不必使用public、abstract修饰  -->
-    <module name="RedundantModifier">
-    </module>
-
-    <!--- 字符串比较必须使用 equals() -->
-    <module name="StringLiteralEquality">
-    </module>
-
-    <!-- if-else嵌套语句个数 最多4层 -->
-    <module name="NestedIfDepth">
-      <property name="max" value="3"/>
-    </module>
-
-    <!-- try-catch 嵌套语句个数 最多2层 -->
-    <module name="NestedTryDepth">
-      <property name="max" value="2"/>
-    </module>
-
-    <!-- 返回个数 -->
-    <module name="ReturnCount">
-      <property name="max" value="5"/>
-      <property name="format" value="^$"/>
-    </module>
-
-  </module>
-
-</module>
\ No newline at end of file
+<code_scheme name="tinye_code_style" version="173">
+  <JavaCodeStyleSettings>
+    <option name="CLASS_COUNT_TO_USE_IMPORT_ON_DEMAND" value="999" />
+    <option name="NAMES_COUNT_TO_USE_IMPORT_ON_DEMAND" value="999" />
+    <option name="PACKAGES_TO_USE_IMPORT_ON_DEMAND">
+      <value />
+    </option>
+    <option name="IMPORT_LAYOUT_TABLE">
+      <value>
+        <emptyLine />
+        <package name="" withSubpackages="true" static="true" />
+        <emptyLine />
+        <package name="com" withSubpackages="true" static="false" />
+        <emptyLine />
+        <package name="" withSubpackages="true" static="false" />
+        <emptyLine />
+        <package name="net" withSubpackages="true" static="false" />
+        <emptyLine />
+        <package name="org" withSubpackages="true" static="false" />
+        <emptyLine />
+        <package name="java" withSubpackages="true" static="false" />
+        <emptyLine />
+        <package name="javax" withSubpackages="true" static="false" />
+        <emptyLine />
+      </value>
+    </option>
+  </JavaCodeStyleSettings>
+  <codeStyleSettings language="JAVA">
+    <option name="LAMBDA_BRACE_STYLE" value="3" />
+  </codeStyleSettings>
+</code_scheme>
\ No newline at end of file

From 7d231981aeb127a5a0131649d8c3e188b3594677 Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Fri, 10 Jul 2026 04:32:59 -0700
Subject: [PATCH 10/19] fix:Checkstyle check

---
 checkstyle/huawei-checkstyle.xml | 298 +++++++++++++++++++++++++++----
 1 file changed, 267 insertions(+), 31 deletions(-)

diff --git a/checkstyle/huawei-checkstyle.xml b/checkstyle/huawei-checkstyle.xml
index c97cd6fd..897c4e52 100644
--- a/checkstyle/huawei-checkstyle.xml
+++ b/checkstyle/huawei-checkstyle.xml
@@ -1,31 +1,267 @@
-<code_scheme name="tinye_code_style" version="173">
-  <JavaCodeStyleSettings>
-    <option name="CLASS_COUNT_TO_USE_IMPORT_ON_DEMAND" value="999" />
-    <option name="NAMES_COUNT_TO_USE_IMPORT_ON_DEMAND" value="999" />
-    <option name="PACKAGES_TO_USE_IMPORT_ON_DEMAND">
-      <value />
-    </option>
-    <option name="IMPORT_LAYOUT_TABLE">
-      <value>
-        <emptyLine />
-        <package name="" withSubpackages="true" static="true" />
-        <emptyLine />
-        <package name="com" withSubpackages="true" static="false" />
-        <emptyLine />
-        <package name="" withSubpackages="true" static="false" />
-        <emptyLine />
-        <package name="net" withSubpackages="true" static="false" />
-        <emptyLine />
-        <package name="org" withSubpackages="true" static="false" />
-        <emptyLine />
-        <package name="java" withSubpackages="true" static="false" />
-        <emptyLine />
-        <package name="javax" withSubpackages="true" static="false" />
-        <emptyLine />
-      </value>
-    </option>
-  </JavaCodeStyleSettings>
-  <codeStyleSettings language="JAVA">
-    <option name="LAMBDA_BRACE_STYLE" value="3" />
-  </codeStyleSettings>
-</code_scheme>
\ No newline at end of file
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE module PUBLIC "-//Puppy Crawl//DTD Check Configuration 1.2//EN" "http://www.puppycrawl.com/dtds/configuration_1_2.dtd">
+
+<!-- Generated by RHY @will_awoke -->
+
+<module name="Checker">
+
+  <property name="charset" value="UTF-8"/>
+  <property name="severity" value="error"/>
+
+  <!-- Checks for Size Violations.  -->
+  <!-- 检查文件的长度（行） default max=2000 -->
+  <module name="FileLength">
+    <property name="max" value="2500"/>
+  </module>
+
+
+  <module name="TreeWalker">
+
+    <!-- Checks for imports    -->
+    <!-- 必须导入类的完整路径，即不能使用*导入所需的类 -->
+    <module name="AvoidStarImport"/>
+
+    <!-- 检查是否从非法的包中导入了类 illegalPkgs: 定义非法的包名称-->
+    <module name="IllegalImport"/> <!-- defaults to sun.* packages -->
+
+    <!-- 检查是否导入了不必显示导入的类-->
+    <module name="RedundantImport"/>
+
+    <!-- 检查是否导入的包没有使用-->
+    <module name="UnusedImports"/>
+
+
+    <!-- 检查类和接口的javadoc 默认不检查author 和version tags
+      authorFormat: 检查author标签的格式
+			versionFormat: 检查version标签的格式
+			scope: 可以检查的类的范围，例如：public只能检查public修饰的类，private可以检查所有的类
+			excludeScope: 不能检查的类的范围，例如：public，public的类将不被检查，但访问权限小于public的类仍然会检查，其他的权限以此类推
+			tokens: 该属性适用的类型，例如：CLASS_DEF,INTERFACE_DEF -->
+    <module name="JavadocType">
+      <property name="authorFormat" value="\S"/>
+      <property name="scope" value="protected"/>
+      <property name="tokens" value="CLASS_DEF,INTERFACE_DEF"/>
+    </module>
+
+    <!-- 检查方法的javadoc的注释
+			scope: 可以检查的方法的范围，例如：public只能检查public修饰的方法，private可以检查所有的方法
+			allowMissingParamTags: 是否忽略对参数注释的检查
+			allowMissingThrowsTags: 是否忽略对throws注释的检查
+			allowMissingReturnTag: 是否忽略对return注释的检查 -->
+    <module name="JavadocMethod">
+      <property name="scope" value="private"/>
+      <property name="allowMissingParamTags" value="false"/>
+      <property name="allowMissingThrowsTags" value="false"/>
+      <property name="allowMissingReturnTag" value="false"/>
+      <property name="tokens" value="METHOD_DEF"/>
+      <property name="allowUndeclaredRTE" value="true"/>
+      <property name="allowThrowsTagsForSubclasses" value="true"/>
+
+    </module>
+
+    <!-- 检查类变量的注释
+			scope: 检查变量的范围，例如：public只能检查public修饰的变量，private可以检查所有的变量 -->
+    <module name="JavadocVariable">
+      <property name="scope" value="private"/>
+    </module>
+
+    <!--option: 定义左大括号'{'显示位置，eol在同一行显示，nl在下一行显示
+      maxLineLength: 大括号'{'所在行行最多容纳的字符数
+      tokens: 该属性适用的类型，例：CLASS_DEF,INTERFACE_DEF,METHOD_DEF,CTOR_DEF -->
+    <module name="LeftCurly">
+      <property name="option" value="nl"/>
+    </module>
+
+    <!-- NeedBraces 检查是否应该使用括号的地方没有加括号
+      tokens: 定义检查的类型 -->
+    <module name="NeedBraces"/>
+
+    <!-- Checks the placement of right curly braces ('}') for  else, try, and catch tokens. The policy to verify is specified using property  option.
+      option: 右大括号是否单独一行显示
+      tokens: 定义检查的类型  -->
+    <module name="RightCurly">
+      <property name="option" value="alone"/>
+    </module>
+
+    <!-- 检查在重写了equals方法后是否重写了hashCode方法 -->
+    <module name="EqualsHashCode"/>
+
+    <!--  Checks for illegal instantiations where a factory method is preferred.
+      Rationale: Depending on the project, for some classes it might be preferable to create instances through factory methods rather than calling the constructor.
+      A simple example is the java.lang.Boolean class. In order to save memory and CPU cycles, it is preferable to use the predefined constants TRUE and FALSE. Constructor invocations should be replaced by calls to Boolean.valueOf().
+      Some extremely performance sensitive projects may require the use of factory methods for other classes as well, to enforce the usage of number caches or object pools. -->
+    <module name="IllegalInstantiation">
+      <property name="classes" value="java.lang.Boolean"/>
+    </module>
+
+    <!-- Checks for Naming Conventions.   命名规范   -->
+    <!-- local, final variables, including catch parameters -->
+    <module name="LocalFinalVariableName"/>
+
+    <!-- local, non-final variables, including catch parameters-->
+    <module name="LocalVariableName"/>
+
+    <!-- static, non-final fields -->
+    <module name="StaticVariableName">
+      <property name="format" value="(^[A-Z0-9_]{0,19}$)"/>
+    </module>
+
+    <!-- packages -->
+    <module name="PackageName" >
+      <property name="format" value="^[a-z]+(\.[a-z][a-z0-9]*)*$"/>
+    </module>
+
+    <!-- classes and interfaces -->
+    <module name="TypeName">
+      <property name="format" value="(^[A-Z][a-zA-Z0-9]{0,19}$)"/>
+    </module>
+
+    <!-- methods -->
+    <module name="MethodName">
+      <property name="format" value="(^[a-z][a-zA-Z0-9]{0,19}$)"/>
+    </module>
+
+    <!-- non-static fields -->
+    <module name="MemberName">
+      <property name="format" value="(^[a-z][a-z0-9][a-zA-Z0-9]{0,19}$)"/>
+    </module>
+
+    <!-- parameters -->
+    <module name="ParameterName">
+      <property name="format" value="(^[a-z][a-zA-Z0-9_]{0,19}$)"/>
+    </module>
+
+    <!-- constants (static,  final fields) -->
+    <module name="ConstantName">
+      <property name="format" value="(^[A-Z0-9_]{0,19}$)"/>
+    </module>
+
+    <!-- 代码缩进   -->
+    <module name="Indentation">
+    </module>
+
+    <!-- Checks for redundant exceptions declared in throws clause such as duplicates, unchecked exceptions or subclasses of another declared exception.
+      检查是否抛出了多余的异常
+    <module name="RedundantThrows">
+    	<property name="logLoadErrors" value="true"/>
+    	<property name="suppressLoadErrors" value="true"/>
+    </module>
+    -->
+
+    <!--  Checks for overly complicated boolean expressions. Currently finds code like  if (b == true), b || true, !false, etc.
+      检查boolean值是否冗余的地方
+      Rationale: Complex boolean logic makes code hard to understand and maintain. -->
+    <module name="SimplifyBooleanExpression"/>
+
+    <!--  Checks for overly complicated boolean return statements. For example the following code
+       检查是否存在过度复杂的boolean返回值
+       if (valid())
+          return false;
+       else
+          return true;
+       could be written as
+          return !valid();
+       The Idea for this Check has been shamelessly stolen from the equivalent PMD rule. -->
+    <module name="SimplifyBooleanReturn"/>
+
+    <!-- Checks that a class which has only private constructors is declared as final.只有私有构造器的类必须声明为final-->
+    <module name="FinalClass"/>
+
+    <!--  Make sure that utility classes (classes that contain only static methods or fields in their API) do not have a public constructor.
+      确保Utils类（只提供static方法和属性的类）没有public构造器。
+      Rationale: Instantiating utility classes does not make sense. Hence the constructors should either be private or (if you want to allow subclassing) protected. A common mistake is forgetting to hide the default constructor.
+      If you make the constructor protected you may want to consider the following constructor implementation technique to disallow instantiating subclasses:
+      public class StringUtils // not final to allow subclassing
+      {
+          protected StringUtils() {
+              throw new UnsupportedOperationException(); // prevents calls from subclass
+          }
+          public static int count(char c, String s) {
+              // ...
+          }
+      }
+   <module name="HideUtilityClassConstructor"/>
+   -->
+
+    <!--  Checks visibility of class members. Only static final members may be public; other class members must be private unless property protectedAllowed or packageAllowed is set.
+      检查class成员属性可见性。只有static final 修饰的成员是可以public的。其他的成员属性必需是private的，除非属性protectedAllowed或者packageAllowed设置了true.
+       Public members are not flagged if the name matches the public member regular expression (contains "^serialVersionUID$" by default). Note: Checkstyle 2 used to include "^f[A-Z][a-zA-Z0-9]*$" in the default pattern to allow CMP for EJB 1.1 with the default settings. With EJB 2.0 it is not longer necessary to have public access for persistent fields, hence the default has been changed.
+       Rationale: Enforce encapsulation. 强制封装 -->
+    <module name="VisibilityModifier"/>
+
+    <!-- 每一行只能定义一个变量 -->
+    <module name="MultipleVariableDeclarations">
+    </module>
+
+    <!-- Checks the style of array type definitions. Some like Java-style: public static void main(String[] args) and some like C-style: public static void main(String args[])
+      检查再定义数组时，采用java风格还是c风格，例如：int[] num是java风格，int num[]是c风格。默认是java风格-->
+    <module name="ArrayTypeStyle">
+    </module>
+
+    <!-- Checks that there are no "magic numbers", where a magic number is a numeric literal that is not defined as a constant. By default, -1, 0, 1, and 2 are not considered to be magic numbers.
+    <module name="MagicNumber">
+    </module>
+    -->
+
+    <!-- A check for TODO: comments. Actually it is a generic regular expression matcher on Java comments. To check for other patterns in Java comments, set property format.
+       检查是否存在TODO（待处理） TODO是javaIDE自动生成的。一般代码写完后要去掉。
+     -->
+    <module name="TodoComment"/>
+
+    <!--  Checks that long constants are defined with an upper ell. That is ' L' and not 'l'. This is in accordance to the Java Language Specification,  Section 3.10.1.
+      检查是否在long类型是否定义了大写的L.字母小写l和数字1（一）很相似。
+      looks a lot like 1. -->
+    <module name="UpperEll"/>
+
+    <!--  Checks that switch statement has "default" clause. 检查switch语句是否有‘default’从句
+       Rationale: It's usually a good idea to introduce a default case in every switch statement.
+       Even if the developer is sure that all currently possible cases are covered, this should be expressed in the default branch,
+        e.g. by using an assertion. This way the code is protected aginst later changes, e.g. introduction of new types in an enumeration type. -->
+    <module name="MissingSwitchDefault"/>
+
+    <!--检查switch中case后是否加入了跳出语句，例如：return、break、throw、continue -->
+    <module name="FallThrough"/>
+
+    <!-- Checks the number of parameters of a method or constructor. max default 7个. -->
+    <module name="ParameterNumber">
+      <property name="max" value="5"/>
+    </module>
+
+
+
+    <!-- Checks for long methods and constructors. max default 150行. max=300 设置长度300 -->
+    <module name="MethodLength">
+      <property name="max" value="300"/>
+    </module>
+
+    <!-- ModifierOrder 检查修饰符的顺序，默认是 public,protected,private,abstract,static,final,transient,volatile,synchronized,native -->
+    <module name="ModifierOrder">
+    </module>
+
+    <!-- 检查是否有多余的修饰符，例如：接口中的方法不必使用public、abstract修饰  -->
+    <module name="RedundantModifier">
+    </module>
+
+    <!--- 字符串比较必须使用 equals() -->
+    <module name="StringLiteralEquality">
+    </module>
+
+    <!-- if-else嵌套语句个数 最多4层 -->
+    <module name="NestedIfDepth">
+      <property name="max" value="3"/>
+    </module>
+
+    <!-- try-catch 嵌套语句个数 最多2层 -->
+    <module name="NestedTryDepth">
+      <property name="max" value="2"/>
+    </module>
+
+    <!-- 返回个数 -->
+    <module name="ReturnCount">
+      <property name="max" value="5"/>
+      <property name="format" value="^$"/>
+    </module>
+
+  </module>
+
+</module>
\ No newline at end of file

From 35a3220d1811fa744376d941302287a9bc35c567 Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Fri, 10 Jul 2026 04:33:21 -0700
Subject: [PATCH 11/19] fix:Checkstyle check

---
 checkstyle/huawei-checkstyle.xml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/checkstyle/huawei-checkstyle.xml b/checkstyle/huawei-checkstyle.xml
index 897c4e52..ee7c30aa 100644
--- a/checkstyle/huawei-checkstyle.xml
+++ b/checkstyle/huawei-checkstyle.xml
@@ -14,6 +14,11 @@
     <property name="max" value="2500"/>
   </module>
 
+  <!-- Checks that property files contain the same keys. -->
+  <!-- 检查**.properties配置文件 是否有相同的key
+  <module name="Translation">
+  </module>
+  -->
 
   <module name="TreeWalker">
 

From 35bfea8f8206551c44a6d756dbf5fa4798e4a95d Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Fri, 10 Jul 2026 04:38:31 -0700
Subject: [PATCH 12/19] fix:Checkstyle check

---
 checkstyle/huawei-checkstyle.xml | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/checkstyle/huawei-checkstyle.xml b/checkstyle/huawei-checkstyle.xml
index ee7c30aa..fa1d4b64 100644
--- a/checkstyle/huawei-checkstyle.xml
+++ b/checkstyle/huawei-checkstyle.xml
@@ -56,11 +56,6 @@
     <module name="JavadocMethod">
       <property name="scope" value="private"/>
       <property name="allowMissingParamTags" value="false"/>
-      <property name="allowMissingThrowsTags" value="false"/>
-      <property name="allowMissingReturnTag" value="false"/>
-      <property name="tokens" value="METHOD_DEF"/>
-      <property name="allowUndeclaredRTE" value="true"/>
-      <property name="allowThrowsTagsForSubclasses" value="true"/>
 
     </module>
 

From 3843ac132749bcc10a75ac17ed19820a7d17871f Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Fri, 10 Jul 2026 04:40:50 -0700
Subject: [PATCH 13/19] fix:Checkstyle check

---
 checkstyle/huawei-checkstyle.xml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/checkstyle/huawei-checkstyle.xml b/checkstyle/huawei-checkstyle.xml
index fa1d4b64..b8052b05 100644
--- a/checkstyle/huawei-checkstyle.xml
+++ b/checkstyle/huawei-checkstyle.xml
@@ -56,7 +56,6 @@
     <module name="JavadocMethod">
       <property name="scope" value="private"/>
       <property name="allowMissingParamTags" value="false"/>
-
     </module>
 
     <!-- 检查类变量的注释

From 3a1b0c933e074fe581b690167983115d187b2600 Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Fri, 10 Jul 2026 05:01:37 -0700
Subject: [PATCH 14/19] fix:Checkstyle check

---
 pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pom.xml b/pom.xml
index 6358bacb..ca4e5a13 100644
--- a/pom.xml
+++ b/pom.xml
@@ -242,7 +242,7 @@
                 <version>3.3.1</version>
                 <configuration>
                     <!-- 指定华为Java编码规范的配置文件 -->
-                    <configLocation>./checkstyle/huawei-checkstyle.xml</configLocation>
+                    <configLocation>./app/src/main/resources/checkstyle.xml</configLocation>
                     <!-- 检查失败时构建失败（阻止CI通过） -->
                     <failOnViolation>true</failOnViolation>
                     <violationSeverity>warning</violationSeverity>

From c52edf33dc3eadeecd8d6308834723aaaf48d2a4 Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Mon, 13 Jul 2026 00:15:56 -0700
Subject: [PATCH 15/19] fix:Checkstyle check

---
 checkstyle/huawei-checkstyle.xml | 238 +++++++++++++------------------
 pom.xml                          |   2 +-
 2 files changed, 100 insertions(+), 140 deletions(-)

diff --git a/checkstyle/huawei-checkstyle.xml b/checkstyle/huawei-checkstyle.xml
index b8052b05..a902a249 100644
--- a/checkstyle/huawei-checkstyle.xml
+++ b/checkstyle/huawei-checkstyle.xml
@@ -1,27 +1,20 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE module PUBLIC "-//Puppy Crawl//DTD Check Configuration 1.2//EN" "http://www.puppycrawl.com/dtds/configuration_1_2.dtd">
 
-<!-- Generated by RHY @will_awoke -->
+<!DOCTYPE module PUBLIC "-//Puppy Crawl//DTD Check Configuration 1.2//EN" "http://www.puppycrawl.com/dtds/configuration_1_2.dtd">
 
+<!-- 指定检查的类和方法命名规则 -->
 <module name="Checker">
 
   <property name="charset" value="UTF-8"/>
-  <property name="severity" value="error"/>
+  <property name="severity" value="warning"/>
 
   <!-- Checks for Size Violations.  -->
   <!-- 检查文件的长度（行） default max=2000 -->
   <module name="FileLength">
     <property name="max" value="2500"/>
   </module>
-
-  <!-- Checks that property files contain the same keys. -->
-  <!-- 检查**.properties配置文件 是否有相同的key
-  <module name="Translation">
-  </module>
-  -->
-
+  <!-- 设定代码格式规则 -->
   <module name="TreeWalker">
-
     <!-- Checks for imports    -->
     <!-- 必须导入类的完整路径，即不能使用*导入所需的类 -->
     <module name="AvoidStarImport"/>
@@ -35,200 +28,163 @@
     <!-- 检查是否导入的包没有使用-->
     <module name="UnusedImports"/>
 
-
     <!-- 检查类和接口的javadoc 默认不检查author 和version tags
-      authorFormat: 检查author标签的格式
-			versionFormat: 检查version标签的格式
-			scope: 可以检查的类的范围，例如：public只能检查public修饰的类，private可以检查所有的类
-			excludeScope: 不能检查的类的范围，例如：public，public的类将不被检查，但访问权限小于public的类仍然会检查，其他的权限以此类推
-			tokens: 该属性适用的类型，例如：CLASS_DEF,INTERFACE_DEF -->
+     authorFormat: 检查author标签的格式
+    versionFormat: 检查version标签的格式
+    scope: 可以检查的类的范围，例如：public只能检查public修饰的类，private可以检查所有的类
+    excludeScope: 不能检查的类的范围，例如：public，public的类将不被检查，但访问权限小于public的类仍然会检查，其他的权限以此类推
+    tokens: 该属性适用的类型，例如：CLASS_DEF,INTERFACE_DEF -->
     <module name="JavadocType">
-      <property name="authorFormat" value="\S"/>
       <property name="scope" value="protected"/>
       <property name="tokens" value="CLASS_DEF,INTERFACE_DEF"/>
     </module>
 
     <!-- 检查方法的javadoc的注释
-			scope: 可以检查的方法的范围，例如：public只能检查public修饰的方法，private可以检查所有的方法
-			allowMissingParamTags: 是否忽略对参数注释的检查
-			allowMissingThrowsTags: 是否忽略对throws注释的检查
-			allowMissingReturnTag: 是否忽略对return注释的检查 -->
+   scope: 可以检查的方法的范围，例如：public只能检查public修饰的方法，private可以检查所有的方法
+   allowMissingParamTags: 是否忽略对参数注释的检查
+   allowMissingThrowsTags: 是否忽略对throws注释的检查
+   allowMissingReturnTag: 是否忽略对return注释的检查 -->
     <module name="JavadocMethod">
-      <property name="scope" value="private"/>
       <property name="allowMissingParamTags" value="false"/>
+      <property name="allowMissingReturnTag" value="false"/>
+      <property name="tokens" value="METHOD_DEF"/>
     </module>
-
-    <!-- 检查类变量的注释
-			scope: 检查变量的范围，例如：public只能检查public修饰的变量，private可以检查所有的变量 -->
-    <module name="JavadocVariable">
-      <property name="scope" value="private"/>
-    </module>
-
     <!--option: 定义左大括号'{'显示位置，eol在同一行显示，nl在下一行显示
-      maxLineLength: 大括号'{'所在行行最多容纳的字符数
-      tokens: 该属性适用的类型，例：CLASS_DEF,INTERFACE_DEF,METHOD_DEF,CTOR_DEF -->
+          maxLineLength: 大括号'{'所在行行最多容纳的字符数
+          tokens: 该属性适用的类型，例：CLASS_DEF,INTERFACE_DEF,METHOD_DEF,CTOR_DEF -->
     <module name="LeftCurly">
-      <property name="option" value="nl"/>
+      <property name="option" value="eol"/>
     </module>
 
-    <!-- NeedBraces 检查是否应该使用括号的地方没有加括号
-      tokens: 定义检查的类型 -->
-    <module name="NeedBraces"/>
-
-    <!-- Checks the placement of right curly braces ('}') for  else, try, and catch tokens. The policy to verify is specified using property  option.
-      option: 右大括号是否单独一行显示
-      tokens: 定义检查的类型  -->
+    <!-- 检查 else、try 和 catch 关键字后的右大括号 (}) 放置位置。验证的规则通过 option 属性指定。
+        option: 右大括号是否单独一行显示
+        tokens: 定义要检查的类型
     <module name="RightCurly">
-      <property name="option" value="alone"/>
-    </module>
+        <property name="option" value="alone"/>
+    </module> -->
 
-    <!-- 检查在重写了equals方法后是否重写了hashCode方法 -->
+    <!-- 检查在重写了 `equals` 方法后是否重写了 `hashCode` 方法 -->
     <module name="EqualsHashCode"/>
 
-    <!--  Checks for illegal instantiations where a factory method is preferred.
-      Rationale: Depending on the project, for some classes it might be preferable to create instances through factory methods rather than calling the constructor.
-      A simple example is the java.lang.Boolean class. In order to save memory and CPU cycles, it is preferable to use the predefined constants TRUE and FALSE. Constructor invocations should be replaced by calls to Boolean.valueOf().
-      Some extremely performance sensitive projects may require the use of factory methods for other classes as well, to enforce the usage of number caches or object pools. -->
+    <!-- 检查非法实例化，建议使用工厂方法。
+         原因：根据项目需求，对于某些类，通过工厂方法来创建实例可能比直接调用构造函数更为优选。
+         一个简单的例子是 `java.lang.Boolean` 类。为了节省内存和 CPU 循环，优先使用预定义常量 `TRUE` 和 `FALSE`。应将构造函数调用替换为 `Boolean.valueOf()` 方法的调用。
+         一些对性能非常敏感的项目可能也要求为其他类使用工厂方法，以强制使用数字缓存或对象池。 -->
     <module name="IllegalInstantiation">
       <property name="classes" value="java.lang.Boolean"/>
     </module>
 
-    <!-- Checks for Naming Conventions.   命名规范   -->
-    <!-- local, final variables, including catch parameters -->
+    <!-- 检查命名规范 -->
+    <!-- 本地的 final 变量，包括 catch 参数 -->
     <module name="LocalFinalVariableName"/>
 
-    <!-- local, non-final variables, including catch parameters-->
-    <module name="LocalVariableName"/>
-
-    <!-- static, non-final fields -->
+    <!-- 静态的非 final 字段 -->
     <module name="StaticVariableName">
       <property name="format" value="(^[A-Z0-9_]{0,19}$)"/>
     </module>
 
-    <!-- packages -->
-    <module name="PackageName" >
+    <!-- 包名 -->
+    <module name="PackageName">
       <property name="format" value="^[a-z]+(\.[a-z][a-z0-9]*)*$"/>
     </module>
+    <!-- 类名应该大写并采用驼峰命名法 -->
+    <module name="TypeName"/>
 
-    <!-- classes and interfaces -->
-    <module name="TypeName">
-      <property name="format" value="(^[A-Z][a-zA-Z0-9]{0,19}$)"/>
-    </module>
+    <!-- 方法名应该采用驼峰命名法 -->
+    <module name="MethodName"/>
 
-    <!-- methods -->
-    <module name="MethodName">
-      <property name="format" value="(^[a-z][a-zA-Z0-9]{0,19}$)"/>
+    <!-- 变量名采用小写字母并使用下划线分隔 -->
+    <module name="LocalVariableName">
+      <property name="format" value="^[a-z][a-z0-9]*(_[a-z0-9]+)*$"/>
     </module>
 
-    <!-- non-static fields -->
+    <!-- 常量名全大写并使用下划线分隔 -->
+    <!--        <module name="FieldName">-->
+    <!--            <property name="format" value="^[a-z][a-zA-Z0-9]*$"/>-->
+    <!--            <property name="allowMultiple" value="false"/>-->
+    <!--        </module>-->
+
+    <!-- 检查类的继承结构是否符合规范 -->
+    <module name="AbstractClassName"/>
+
+    <!-- 配置 Indentation 模块 -->
+    <module name="Indentation"/>
+
+    <!-- 每个方法后必须有空行 -->
+    <module name="MethodParamPad"/>
+
+    <!-- 强制使用强制括号 -->
+    <module name="NeedBraces"/>
+
+    <!-- 禁止在代码中使用多余的空格 -->
+    <module name="WhitespaceAfter"/>
+
+    <!--检查switch中case后是否加入了跳出语句，例如：return、break、throw、continue -->
+    <module name="FallThrough"/>
+
+    <!-- 检查方法或构造函数的参数数量，默认最大为7个。 -->
+    <module name="ParameterNumber">
+      <property name="max" value="5"/>
+    </module>
+    <!-- 非静态字段 -->
     <module name="MemberName">
       <property name="format" value="(^[a-z][a-z0-9][a-zA-Z0-9]{0,19}$)"/>
     </module>
 
-    <!-- parameters -->
+    <!-- 参数 -->
     <module name="ParameterName">
       <property name="format" value="(^[a-z][a-zA-Z0-9_]{0,19}$)"/>
     </module>
 
-    <!-- constants (static,  final fields) -->
+    <!-- 常量（静态 final 字段） -->
     <module name="ConstantName">
       <property name="format" value="(^[A-Z0-9_]{0,19}$)"/>
     </module>
 
-    <!-- 代码缩进   -->
-    <module name="Indentation">
-    </module>
-
-    <!-- Checks for redundant exceptions declared in throws clause such as duplicates, unchecked exceptions or subclasses of another declared exception.
-      检查是否抛出了多余的异常
-    <module name="RedundantThrows">
-    	<property name="logLoadErrors" value="true"/>
-    	<property name="suppressLoadErrors" value="true"/>
-    </module>
-    -->
-
-    <!--  Checks for overly complicated boolean expressions. Currently finds code like  if (b == true), b || true, !false, etc.
-      检查boolean值是否冗余的地方
-      Rationale: Complex boolean logic makes code hard to understand and maintain. -->
+    <!-- 检查布尔表达式是否可以简化。 -->
     <module name="SimplifyBooleanExpression"/>
 
-    <!--  Checks for overly complicated boolean return statements. For example the following code
-       检查是否存在过度复杂的boolean返回值
-       if (valid())
-          return false;
-       else
-          return true;
-       could be written as
-          return !valid();
-       The Idea for this Check has been shamelessly stolen from the equivalent PMD rule. -->
+    <!-- 检查是否存在过度复杂的布尔返回值。例如，以下代码
+         if (valid())
+            return false;
+         else
+            return true;
+         可以简化为
+            return !valid(); -->
     <module name="SimplifyBooleanReturn"/>
-
-    <!-- Checks that a class which has only private constructors is declared as final.只有私有构造器的类必须声明为final-->
-    <module name="FinalClass"/>
-
-    <!--  Make sure that utility classes (classes that contain only static methods or fields in their API) do not have a public constructor.
-      确保Utils类（只提供static方法和属性的类）没有public构造器。
-      Rationale: Instantiating utility classes does not make sense. Hence the constructors should either be private or (if you want to allow subclassing) protected. A common mistake is forgetting to hide the default constructor.
-      If you make the constructor protected you may want to consider the following constructor implementation technique to disallow instantiating subclasses:
-      public class StringUtils // not final to allow subclassing
-      {
-          protected StringUtils() {
-              throw new UnsupportedOperationException(); // prevents calls from subclass
-          }
-          public static int count(char c, String s) {
-              // ...
-          }
-      }
-   <module name="HideUtilityClassConstructor"/>
-   -->
-
-    <!--  Checks visibility of class members. Only static final members may be public; other class members must be private unless property protectedAllowed or packageAllowed is set.
-      检查class成员属性可见性。只有static final 修饰的成员是可以public的。其他的成员属性必需是private的，除非属性protectedAllowed或者packageAllowed设置了true.
-       Public members are not flagged if the name matches the public member regular expression (contains "^serialVersionUID$" by default). Note: Checkstyle 2 used to include "^f[A-Z][a-zA-Z0-9]*$" in the default pattern to allow CMP for EJB 1.1 with the default settings. With EJB 2.0 it is not longer necessary to have public access for persistent fields, hence the default has been changed.
-       Rationale: Enforce encapsulation. 强制封装 -->
+    <!-- 检查类成员的可见性。只有 static final 修饰的成员可以是 public 的；其他的成员属性必须是 private 的，除非属性 protectedAllowed 或者 packageAllowed 被设置为 true。
+         如果公共成员的名称匹配公共成员正则表达式（默认包含 "^serialVersionUID$"），则不会标记为违规。
+         注意：Checkstyle 2 之前的默认模式包括了 "^f[A-Z][a-zA-Z0-9]*$"，允许 EJB 1.1 的 CMP 使用默认设置。
+         对于 EJB 2.0，不再需要为持久字段提供公共访问权限，因此默认模式已被更改。
+         理由：强制封装。-->
     <module name="VisibilityModifier"/>
 
     <!-- 每一行只能定义一个变量 -->
     <module name="MultipleVariableDeclarations">
     </module>
 
-    <!-- Checks the style of array type definitions. Some like Java-style: public static void main(String[] args) and some like C-style: public static void main(String args[])
-      检查再定义数组时，采用java风格还是c风格，例如：int[] num是java风格，int num[]是c风格。默认是java风格-->
+    <!-- 检查数组类型定义的风格。有些采用 Java 风格，例如：public static void main(String[] args)，有些采用 C 风格，例如：public static void main(String args[])
+         检查定义数组时采用 Java 风格还是 C 风格，例如：int[] num 是 Java 风格，int num[] 是 C 风格。默认是 Java 风格 -->
     <module name="ArrayTypeStyle">
     </module>
 
-    <!-- Checks that there are no "magic numbers", where a magic number is a numeric literal that is not defined as a constant. By default, -1, 0, 1, and 2 are not considered to be magic numbers.
+    <!-- 检查是否存在 "魔法数字"，魔法数字是没有定义为常量的数值字面量。默认情况下，-1、0、1 和 2 不被视为魔法数字。
     <module name="MagicNumber">
     </module>
     -->
 
-    <!-- A check for TODO: comments. Actually it is a generic regular expression matcher on Java comments. To check for other patterns in Java comments, set property format.
-       检查是否存在TODO（待处理） TODO是javaIDE自动生成的。一般代码写完后要去掉。
-     -->
+    <!-- 检查是否存在 TODO（待处理）注释。实际上，这是对 Java 注释的通用正则表达式匹配器。要检查 Java 注释中的其他模式，请设置属性 format。
+         检查是否存在 TODO（待处理）注释。TODO 是 Java IDE 自动生成的，代码写完后通常会去掉。-->
     <module name="TodoComment"/>
 
-    <!--  Checks that long constants are defined with an upper ell. That is ' L' and not 'l'. This is in accordance to the Java Language Specification,  Section 3.10.1.
-      检查是否在long类型是否定义了大写的L.字母小写l和数字1（一）很相似。
-      looks a lot like 1. -->
+    <!-- 检查 long 类型常量是否使用大写的 'L' 来表示，而不是小写的 'l'。这是遵循 Java 语言规范，第 3.10.1 节。
+         检查 long 类型常量是否定义了大写的 'L'。字母小写的 l 与数字 1（或者一）非常相似。 -->
     <module name="UpperEll"/>
 
-    <!--  Checks that switch statement has "default" clause. 检查switch语句是否有‘default’从句
-       Rationale: It's usually a good idea to introduce a default case in every switch statement.
-       Even if the developer is sure that all currently possible cases are covered, this should be expressed in the default branch,
-        e.g. by using an assertion. This way the code is protected aginst later changes, e.g. introduction of new types in an enumeration type. -->
-    <module name="MissingSwitchDefault"/>
-
-    <!--检查switch中case后是否加入了跳出语句，例如：return、break、throw、continue -->
-    <module name="FallThrough"/>
-
-    <!-- Checks the number of parameters of a method or constructor. max default 7个. -->
-    <module name="ParameterNumber">
-      <property name="max" value="5"/>
-    </module>
-
-
+    <!-- 检查一个只有私有构造器的类是否声明为 final。只有私有构造器的类必须声明为 final -->
+    <module name="FinalClass"/>
 
-    <!-- Checks for long methods and constructors. max default 150行. max=300 设置长度300 -->
+    <!-- 检查方法和构造函数是否过长。默认最大行数为 150 行。可以通过设置 max=300 来调整最大行数为 300。 -->
     <module name="MethodLength">
       <property name="max" value="300"/>
     </module>
@@ -260,7 +216,11 @@
       <property name="max" value="5"/>
       <property name="format" value="^$"/>
     </module>
-
   </module>
 
+  <!-- LineLength 配置独立于 TreeWalker -->
+  <module name="LineLength">
+    <property name="max" value="120"/>
+    <property name="ignorePattern" value="^package|^import"/>
+  </module>
 </module>
\ No newline at end of file
diff --git a/pom.xml b/pom.xml
index ca4e5a13..6358bacb 100644
--- a/pom.xml
+++ b/pom.xml
@@ -242,7 +242,7 @@
                 <version>3.3.1</version>
                 <configuration>
                     <!-- 指定华为Java编码规范的配置文件 -->
-                    <configLocation>./app/src/main/resources/checkstyle.xml</configLocation>
+                    <configLocation>./checkstyle/huawei-checkstyle.xml</configLocation>
                     <!-- 检查失败时构建失败（阻止CI通过） -->
                     <failOnViolation>true</failOnViolation>
                     <violationSeverity>warning</violationSeverity>

From 929462f67f1a9807f24ea7a3f7242e0a64b8c4af Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Mon, 13 Jul 2026 02:24:36 -0700
Subject: [PATCH 16/19] fix:Checkstyle check

---
 checkstyle/huawei-checkstyle.xml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/checkstyle/huawei-checkstyle.xml b/checkstyle/huawei-checkstyle.xml
index a902a249..a2a60652 100644
--- a/checkstyle/huawei-checkstyle.xml
+++ b/checkstyle/huawei-checkstyle.xml
@@ -4,7 +4,6 @@
 
 <!-- 指定检查的类和方法命名规则 -->
 <module name="Checker">
-
   <property name="charset" value="UTF-8"/>
   <property name="severity" value="warning"/>
 

From 989abaf6af2f464980222202d4817c65799d3626 Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Mon, 13 Jul 2026 03:33:35 -0700
Subject: [PATCH 17/19] fix:Checkstyle check

---
 .github/scripts/checkstyle-pr.sh | 110 +++++++++++++++++++++++++++++++
 .github/workflows/checkstyle.yml |  10 ++-
 pom.xml                          |   2 +-
 3 files changed, 119 insertions(+), 3 deletions(-)
 create mode 100644 .github/scripts/checkstyle-pr.sh

diff --git a/.github/scripts/checkstyle-pr.sh b/.github/scripts/checkstyle-pr.sh
new file mode 100644
index 00000000..a56185fa
--- /dev/null
+++ b/.github/scripts/checkstyle-pr.sh
@@ -0,0 +1,110 @@
+#!/bin/bash
+# ============================================================
+# checkstyle-pr.sh - 增量 Checkstyle 检查（仅报告，不阻断构建）
+# 用途：扫描 PR/commit 中变更的 Java 文件，生成违规报告
+# ============================================================
+
+set -e  # 遇到错误立即退出（但我们会特殊处理 mvn 的返回）
+
+echo "========================================"
+echo "  Checkstyle PR 增量检查 (仅报告)"
+echo "========================================"
+
+# 1. 确定对比的目标分支
+if [ -n "$GITHUB_BASE_REF" ]; then
+    # GitHub Actions 环境：PR 事件
+    BASE_BRANCH="origin/$GITHUB_BASE_REF"
+    echo "🔍 检测到 PR 事件，目标分支: $GITHUB_BASE_REF"
+elif [ -n "$GITHUB_REF" ] && [ "$GITHUB_EVENT_NAME" == "push" ]; then
+    # push 事件，对比上一次提交
+    BASE_BRANCH="HEAD^"
+    echo "🔍 检测到 Push 事件，对比上一次提交"
+else
+    # 本地运行：默认对比 origin/main，如果不存在则尝试 origin/develop
+    if git rev-parse --verify origin/main >/dev/null 2>&1; then
+        BASE_BRANCH="origin/main"
+    elif git rev-parse --verify origin/develop >/dev/null 2>&1; then
+        BASE_BRANCH="origin/develop"
+    else
+        echo "❌ 无法确定目标分支，请指定 BASE_BRANCH 环境变量或在 Git 仓库中设置远程分支。"
+        exit 1
+    fi
+    echo "🔍 本地运行模式，对比分支: $BASE_BRANCH"
+fi
+
+# 2. 确保目标分支存在（如果是远程分支，先 fetch）
+if [[ "$BASE_BRANCH" == origin/* ]] && ! git rev-parse --verify "$BASE_BRANCH" >/dev/null 2>&1; then
+    echo "⬇️ 正在 fetch 远程分支 $BASE_BRANCH ..."
+    git fetch origin "${BASE_BRANCH#origin/}"
+fi
+
+# 3. 获取变更的 Java 文件列表
+CHANGED_FILES=$(git diff --name-only "$BASE_BRANCH" HEAD 2>/dev/null | grep '\.java$' || true)
+
+if [ -z "$CHANGED_FILES" ]; then
+    echo "✅ 本次没有变更 Java 文件，跳过检查。"
+    exit 0
+fi
+
+echo "📝 本次变更的 Java 文件："
+echo "$CHANGED_FILES"
+echo "----------------------------------------"
+
+# 4. 将文件列表转为逗号分隔（用于 Maven 参数）
+FILES_LIST=$(echo "$CHANGED_FILES" | tr '\n' ',' | sed 's/,$//')
+
+# 5. 执行 Checkstyle（生成报告，不阻断）
+echo "🚀 开始执行 Checkstyle 增量扫描..."
+set +e  # 暂时关闭错误退出，以便我们自己处理返回值
+mvn checkstyle:checkstyle \
+    -Dcheckstyle.includes="$FILES_LIST" \
+    -Dcheckstyle.excludes="**/test/**/*.java"
+MVN_EXIT=$?
+set -e  # 恢复
+
+# 6. 解析违规数
+VIOLATIONS=0
+REPORT_FILE="target/checkstyle-result.xml"
+if [ -f "$REPORT_FILE" ]; then
+    VIOLATIONS=$(grep -c '<error' "$REPORT_FILE" || true)
+    HTML_REPORT="target/site/checkstyle.html"
+fi
+
+echo "----------------------------------------"
+if [ $VIOLATIONS -eq 0 ]; then
+    echo "✅ 所有变更文件符合编码规范！"
+else
+    echo "⚠️ 发现 $VIOLATIONS 个违规项（详见下方摘要和 Artifact 报告）"
+    echo ""
+    echo "📋 违规摘要（前 30 条）："
+    grep '<error' "$REPORT_FILE" | head -30 | sed 's/<error //; s/\/>//' | \
+        sed 's/line="/行号: /; s/column="/列: /; s/severity="/严重性: /; s=message="=信息: =; s=source="//' | \
+        while read -r line; do
+            echo "  $line"
+        done
+fi
+
+# 7. 输出到 GitHub Step Summary（仅在 Actions 环境中有效）
+if [ -n "$GITHUB_STEP_SUMMARY" ]; then
+    {
+        echo "## 📋 Checkstyle 报告摘要"
+        echo ""
+        echo "| 指标 | 结果 |"
+        echo "|------|------|"
+        if [ $VIOLATIONS -eq 0 ]; then
+            echo "| 违规数 | ✅ **0** |"
+        else
+            echo "| 违规数 | ⚠️ **$VIOLATIONS** |"
+        fi
+        echo "| 扫描文件 | **$(echo "$CHANGED_FILES" | wc -l)** 个 Java 文件 |"
+        echo ""
+        if [ -f "$HTML_REPORT" ]; then
+            echo "📄 [查看详细 HTML 报告](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})"
+        fi
+        echo "💡 完整报告作为 Artifact 下载，请查看工作流运行页面。"
+    } >> "$GITHUB_STEP_SUMMARY"
+    echo "✅ Step Summary 已生成"
+fi
+
+# 8. 始终以成功状态退出（不阻断构建）
+exit 0
\ No newline at end of file
diff --git a/.github/workflows/checkstyle.yml b/.github/workflows/checkstyle.yml
index 3d0c1283..8fbd7901 100644
--- a/.github/workflows/checkstyle.yml
+++ b/.github/workflows/checkstyle.yml
@@ -15,6 +15,8 @@ jobs:
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
+        with:
+          fetch-depth: 0   # 必须拉取完整历史，才能比较分支差异
 
       - name: Set up JDK 17
         uses: actions/setup-java@v4
@@ -33,7 +35,9 @@ jobs:
 
       # 直接运行 Checkstyle 检查（不执行完整的 package）
       - name: Run Checkstyle
-        run: mvn checkstyle:check
+        run: bash .github/scripts/checkstyle-pr.sh
+        env:
+          GITHUB_BASE_REF: ${{ github.base_ref }}
 
       # 如果检查失败，仍然上传报告供查看
       - name: Upload Checkstyle report
@@ -41,4 +45,6 @@ jobs:
         uses: actions/upload-artifact@v4
         with:
           name: checkstyle-report
-          path: target/checkstyle-result.xml
+          path: | 
+            target/checkstyle-result.xml
+            target/site/checkstyle.html
diff --git a/pom.xml b/pom.xml
index 6358bacb..a4bdd76f 100644
--- a/pom.xml
+++ b/pom.xml
@@ -244,7 +244,7 @@
                     <!-- 指定华为Java编码规范的配置文件 -->
                     <configLocation>./checkstyle/huawei-checkstyle.xml</configLocation>
                     <!-- 检查失败时构建失败（阻止CI通过） -->
-                    <failOnViolation>true</failOnViolation>
+                    <failOnViolation>false</failOnViolation>
                     <violationSeverity>warning</violationSeverity>
                     <!-- 输出格式 -->
                     <outputFileFormat>xml</outputFileFormat>

From c97a525d8782a4e99b7f07b9029f306a36d30a7a Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Mon, 13 Jul 2026 03:52:40 -0700
Subject: [PATCH 18/19] fix:Checkstyle check

---
 .github/scripts/checkstyle-pr.sh | 200 +++++++++++++++++++++++--------
 1 file changed, 153 insertions(+), 47 deletions(-)

diff --git a/.github/scripts/checkstyle-pr.sh b/.github/scripts/checkstyle-pr.sh
index a56185fa..8f1e2468 100644
--- a/.github/scripts/checkstyle-pr.sh
+++ b/.github/scripts/checkstyle-pr.sh
@@ -1,110 +1,216 @@
 #!/bin/bash
 # ============================================================
-# checkstyle-pr.sh - 增量 Checkstyle 检查（仅报告，不阻断构建）
-# 用途：扫描 PR/commit 中变更的 Java 文件，生成违规报告
+# checkstyle-pr.sh - 真正的增量检查
+# 功能：只报告本次提交中新增或修改行的 Checkstyle 违规
+# 不阻断构建，生成过滤后的报告
 # ============================================================
 
-set -e  # 遇到错误立即退出（但我们会特殊处理 mvn 的返回）
+set -e
 
 echo "========================================"
-echo "  Checkstyle PR 增量检查 (仅报告)"
+echo "  Checkstyle 增量行检查 (只检测新代码)"
 echo "========================================"
 
-# 1. 确定对比的目标分支
+# 1. 确定目标分支
 if [ -n "$GITHUB_BASE_REF" ]; then
-    # GitHub Actions 环境：PR 事件
     BASE_BRANCH="origin/$GITHUB_BASE_REF"
-    echo "🔍 检测到 PR 事件，目标分支: $GITHUB_BASE_REF"
 elif [ -n "$GITHUB_REF" ] && [ "$GITHUB_EVENT_NAME" == "push" ]; then
-    # push 事件，对比上一次提交
     BASE_BRANCH="HEAD^"
-    echo "🔍 检测到 Push 事件，对比上一次提交"
 else
-    # 本地运行：默认对比 origin/main，如果不存在则尝试 origin/develop
     if git rev-parse --verify origin/main >/dev/null 2>&1; then
         BASE_BRANCH="origin/main"
     elif git rev-parse --verify origin/develop >/dev/null 2>&1; then
         BASE_BRANCH="origin/develop"
     else
-        echo "❌ 无法确定目标分支，请指定 BASE_BRANCH 环境变量或在 Git 仓库中设置远程分支。"
+        echo "❌ 无法确定目标分支，请设置 BASE_BRANCH 环境变量。"
         exit 1
     fi
     echo "🔍 本地运行模式，对比分支: $BASE_BRANCH"
 fi
 
-# 2. 确保目标分支存在（如果是远程分支，先 fetch）
-if [[ "$BASE_BRANCH" == origin/* ]] && ! git rev-parse --verify "$BASE_BRANCH" >/dev/null 2>&1; then
-    echo "⬇️ 正在 fetch 远程分支 $BASE_BRANCH ..."
-    git fetch origin "${BASE_BRANCH#origin/}"
-fi
-
-# 3. 获取变更的 Java 文件列表
+# 2. 获取变更的 Java 文件
 CHANGED_FILES=$(git diff --name-only "$BASE_BRANCH" HEAD 2>/dev/null | grep '\.java$' || true)
 
 if [ -z "$CHANGED_FILES" ]; then
-    echo "✅ 本次没有变更 Java 文件，跳过检查。"
+    echo "✅ 没有 Java 文件变更，跳过检查。"
     exit 0
 fi
 
-echo "📝 本次变更的 Java 文件："
+echo "📝 变更的 Java 文件："
 echo "$CHANGED_FILES"
 echo "----------------------------------------"
 
-# 4. 将文件列表转为逗号分隔（用于 Maven 参数）
+# 3. 生成包含变更行号信息的文件 (用于后续过滤)
+echo "🔄 提取变更行号..."
+CHANGE_INFO_FILE=".checkstyle-changes.txt"
+rm -f "$CHANGE_INFO_FILE"
+
+for file in $CHANGED_FILES; do
+    # 获取该文件新增或修改的行号范围（新文件行号）
+    # git diff -U0 输出 unified=0，只显示变更行
+    diff_output=$(git diff -U0 "$BASE_BRANCH" HEAD -- "$file" 2>/dev/null | grep '^@@' || true)
+    if [ -n "$diff_output" ]; then
+        # 解析 @@ -old,count +new,count @@ 提取新行号范围
+        echo "$diff_output" | while read -r line; do
+            # 提取 + 后面的起始行和行数
+            new_info=$(echo "$line" | sed -n 's/.*+\([0-9]*\)\(,[0-9]*\)\?.*/\1 \2/p')
+            if [ -n "$new_info" ]; then
+                start=$(echo "$new_info" | awk '{print $1}')
+                count=$(echo "$new_info" | awk '{print $2}' | sed 's/,//')
+                if [ -z "$count" ]; then
+                    count=1
+                fi
+                # 生成行号范围，例如 file:10-15
+                echo "$file:$start-$((start+count-1))" >> "$CHANGE_INFO_FILE"
+            fi
+        done
+    fi
+done
+
+if [ ! -s "$CHANGE_INFO_FILE" ]; then
+    echo "⚠️ 未提取到变更行号，可能变更只涉及删除或文件重命名，跳过检查。"
+    exit 0
+fi
+
+echo "变更行号信息已保存到 $CHANGE_INFO_FILE"
+
+# 4. 执行 Checkstyle 扫描全部变更文件（生成完整报告）
+echo "🚀 执行 Checkstyle 扫描（生成完整报告）..."
 FILES_LIST=$(echo "$CHANGED_FILES" | tr '\n' ',' | sed 's/,$//')
 
-# 5. 执行 Checkstyle（生成报告，不阻断）
-echo "🚀 开始执行 Checkstyle 增量扫描..."
-set +e  # 暂时关闭错误退出，以便我们自己处理返回值
+set +e
 mvn checkstyle:checkstyle \
     -Dcheckstyle.includes="$FILES_LIST" \
-    -Dcheckstyle.excludes="**/test/**/*.java"
+    -Dcheckstyle.excludes="**/test/**/*.java" \
+    -Dcheckstyle.violationSeverity=warning
 MVN_EXIT=$?
-set -e  # 恢复
+set -e
 
-# 6. 解析违规数
-VIOLATIONS=0
 REPORT_FILE="target/checkstyle-result.xml"
-if [ -f "$REPORT_FILE" ]; then
-    VIOLATIONS=$(grep -c '<error' "$REPORT_FILE" || true)
-    HTML_REPORT="target/site/checkstyle.html"
+if [ ! -f "$REPORT_FILE" ]; then
+    echo "❌ 未生成 Checkstyle 报告，请检查 Maven 配置。"
+    exit 0
+fi
+
+# 5. 过滤报告：只保留变更行上的违规
+echo "🔄 过滤违规，只保留变更行上的问题..."
+FILTERED_REPORT="target/checkstyle-filtered-result.xml"
+FILTERED_VIOLATIONS=0
+
+# 使用 Python 脚本过滤（GitHub Actions 环境自带 python3）
+python3 << EOF
+import sys
+import xml.etree.ElementTree as ET
+
+# 读取变更行信息
+changed_lines = {}
+with open("$CHANGE_INFO_FILE", "r") as f:
+    for line in f:
+        line = line.strip()
+        if not line:
+            continue
+        parts = line.split(':')
+        if len(parts) != 2:
+            continue
+        file = parts[0]
+        range_str = parts[1]
+        start_end = range_str.split('-')
+        if len(start_end) == 2:
+            start = int(start_end[0])
+            end = int(start_end[1])
+            for i in range(start, end+1):
+                changed_lines.setdefault(file, set()).add(i)
+        else:
+            # 单行
+            changed_lines.setdefault(file, set()).add(int(start_end[0]))
+
+# 解析 Checkstyle 报告
+tree = ET.parse("$REPORT_FILE")
+root = tree.getroot()
+
+# 创建过滤后的根
+new_root = ET.Element("checkstyle", attrib=root.attrib)
+
+for file_elem in root.findall("file"):
+    file_name = file_elem.get("name")
+    # 获取相对于项目根目录的路径（可能带有绝对路径，需要规范化）
+    # 简单处理：取文件名部分，但为了匹配，我们只比较文件名（如果路径不同）
+    # 更健壮：使用文件名的 basename 或匹配路径结尾
+    # 这里我们直接匹配字符串，因为 diff 输出的是相对路径，而 Checkstyle 输出绝对路径
+    # 我们尝试使用相对路径匹配
+    changed_set = changed_lines.get(file_name, set())
+    if not changed_set:
+        # 尝试取 basename 匹配
+        base = file_name.split('/')[-1]
+        for key in changed_lines:
+            if key.endswith(base):
+                changed_set = changed_lines[key]
+                break
+
+    new_file = ET.SubElement(new_root, "file", attrib=file_elem.attrib)
+    errors_found = False
+    for error in file_elem.findall("error"):
+        line_num = int(error.get("line", 0))
+        if line_num in changed_set:
+            new_file.append(error)
+            errors_found = True
+    if not errors_found:
+        # 如果该文件没有违规，则移除（但保留空文件无意义，可以跳过）
+        new_root.remove(new_file)
+
+# 写回过滤后的报告
+tree = ET.ElementTree(new_root)
+tree.write("$FILTERED_REPORT", encoding="utf-8", xml_declaration=True)
+EOF
+
+# 6. 统计过滤后的违规数
+if [ -f "$FILTERED_REPORT" ]; then
+    FILTERED_VIOLATIONS=$(grep -c '<error' "$FILTERED_REPORT" || true)
+else
+    FILTERED_VIOLATIONS=0
 fi
 
 echo "----------------------------------------"
-if [ $VIOLATIONS -eq 0 ]; then
-    echo "✅ 所有变更文件符合编码规范！"
+if [ $FILTERED_VIOLATIONS -eq 0 ]; then
+    echo "✅ 新增代码未发现违规！"
 else
-    echo "⚠️ 发现 $VIOLATIONS 个违规项（详见下方摘要和 Artifact 报告）"
+    echo "⚠️ 新增代码中发现 $FILTERED_VIOLATIONS 个违规项（仅统计新提交的行）"
     echo ""
     echo "📋 违规摘要（前 30 条）："
-    grep '<error' "$REPORT_FILE" | head -30 | sed 's/<error //; s/\/>//' | \
+    grep '<error' "$FILTERED_REPORT" | head -30 | sed 's/<error //; s/\/>//' | \
         sed 's/line="/行号: /; s/column="/列: /; s/severity="/严重性: /; s=message="=信息: =; s=source="//' | \
         while read -r line; do
             echo "  $line"
         done
 fi
 
-# 7. 输出到 GitHub Step Summary（仅在 Actions 环境中有效）
+# 7. 输出到 GitHub Step Summary
 if [ -n "$GITHUB_STEP_SUMMARY" ]; then
     {
-        echo "## 📋 Checkstyle 报告摘要"
+        echo "## 📋 Checkstyle 增量行报告"
         echo ""
         echo "| 指标 | 结果 |"
         echo "|------|------|"
-        if [ $VIOLATIONS -eq 0 ]; then
-            echo "| 违规数 | ✅ **0** |"
+        if [ $FILTERED_VIOLATIONS -eq 0 ]; then
+            echo "| 新增代码违规数 | ✅ **0** |"
         else
-            echo "| 违规数 | ⚠️ **$VIOLATIONS** |"
+            echo "| 新增代码违规数 | ⚠️ **$FILTERED_VIOLATIONS** |"
         fi
-        echo "| 扫描文件 | **$(echo "$CHANGED_FILES" | wc -l)** 个 Java 文件 |"
+        echo "| 扫描文件 | **$(echo "$CHANGED_FILES" | wc -l)** 个变更 Java 文件 |"
+        echo "| 检查范围 | 仅新增或修改的行 |"
         echo ""
-        if [ -f "$HTML_REPORT" ]; then
-            echo "📄 [查看详细 HTML 报告](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})"
-        fi
-        echo "💡 完整报告作为 Artifact 下载，请查看工作流运行页面。"
+        echo "📄 [下载完整报告（所有文件）](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})"
+        echo "📄 [下载过滤后报告（仅新增行）](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})"
     } >> "$GITHUB_STEP_SUMMARY"
-    echo "✅ Step Summary 已生成"
+    echo "✅ Step Summary 已更新"
 fi
 
-# 8. 始终以成功状态退出（不阻断构建）
+# 8. 替换原始报告为过滤后的报告（以便 Artifact 上传只包含过滤结果）
+# 但为了保留完整报告，我们不上传过滤后的，而是上传原始和过滤两份。
+# 在 YAML 中，我们会上传整个 target/ 下的相关文件，所以无所谓。
+
+# 9. 清理临时文件
+rm -f "$CHANGE_INFO_FILE"
+
+# 10. 始终以成功状态退出
 exit 0
\ No newline at end of file

From 082e950f2b40d9f981fad8b3f170946eb2c8c494 Mon Sep 17 00:00:00 2001
From: msslulu <1484036491@qq.com>
Date: Mon, 13 Jul 2026 04:11:07 -0700
Subject: [PATCH 19/19] fix:Checkstyle check

---
 .github/workflows/checkstyle.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/checkstyle.yml b/.github/workflows/checkstyle.yml
index 8fbd7901..176c5e7b 100644
--- a/.github/workflows/checkstyle.yml
+++ b/.github/workflows/checkstyle.yml
@@ -46,5 +46,5 @@ jobs:
         with:
           name: checkstyle-report
           path: | 
-            target/checkstyle-result.xml
-            target/site/checkstyle.html
+            */target/checkstyle-result.xml
+            */target/site/checkstyle.html