[incubator-inlong-website] branch master updated: [INLONG-2398][WEBSITE][Improve] Add the requirement to execute mvn test (#275)

[do...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

dockerzhang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-inlong-website.git


The following commit(s) were added to refs/heads/master by this push:
     new 6bfe2fe  [INLONG-2398][WEBSITE][Improve] Add the requirement to execute mvn test (#275)
6bfe2fe is described below

commit 6bfe2fe0369ab1ebb92f371114ab62bb7191c825
Author: gosonzhang <46...@qq.com>
AuthorDate: Sun Feb 6 18:22:22 2022 +0800

    [INLONG-2398][WEBSITE][Improve] Add the requirement to execute mvn test (#275)
---
 development/how-to-verify.md                                        | 6 ++++++
 .../current/how-to-verify.md                                        | 6 ++++++
 2 files changed, 12 insertions(+)

diff --git a/development/how-to-verify.md b/development/how-to-verify.md
index 2b95bb7..56bb712 100644
--- a/development/how-to-verify.md
+++ b/development/how-to-verify.md
@@ -134,6 +134,12 @@ Unzip `apache-inlong-${release_version}-src.tar.gz` and check as follows:
 - [ ] The single test can run through.
 - [ ] Building is OK.
 
+Attentions:
+   In the process of practice, it is found that many troublesome problems affect our version verification. The following processing is for reference:
+   - Clean up the local repository before verifying the version;
+   - The compilation commands are not limited, but since the modules in the project are dockerized, "mvn clean package install" is recommended for the first compilation, other recommended operations include "mvn clean compile", "mvn clean package";
+   - When executing unit tests, you should run them separately with "mvn clean test" to ensure that there are no hidden problems.
+
 ### 2.5 Check the binary package (if the binary package is included)
   Unzip `apache-inlong-client-${release_version}-src.tar.gz` and `
   apache-inlong-server-${release_version}-src.tar.gz`, check as follows:
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-development/current/how-to-verify.md b/i18n/zh-CN/docusaurus-plugin-content-docs-development/current/how-to-verify.md
index a431e95..1c764c6 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-development/current/how-to-verify.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-development/current/how-to-verify.md
@@ -123,6 +123,12 @@ for i in *.tar.gz.sha512; do echo $i; sha512sum -c $i; done
   - 源码是否能够正常编译
   - 单测是否能够跑通
   - ....
+  
+  注意事项：
+  在实践过程中，发现比较多的困扰问题影响到我们的版本验证，如下处理供参考：
+  - 校验版本前先清理掉本地仓库；
+  - 编译方法不限制，但由于项目里的模块做了docker化处理，首次编译建议先“mvn clean package install”，其他推荐的操作还有“mvn compile”，“mvn clean package”；
+  - 执行单元测试时，大家要用“mvn clean test”单独运行，确保没有隐藏问题。
 
 ### 2.5 检查二进制包(如果上传了二进制包)
   解压缩`apache-inlong-client-${release_version}-src.tar.gz`和`