You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by wu...@apache.org on 2021/06/16 08:00:16 UTC
[shardingsphere] branch master updated: Update mvn command in doc
(#10834)
This is an automated email from the ASF dual-hosted git repository.
wuweijie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git
The following commit(s) were added to refs/heads/master by this push:
new 2738978 Update mvn command in doc (#10834)
2738978 is described below
commit 2738978cc0e3535784576697c16a957b11d6a87d
Author: Liang Zhang <te...@163.com>
AuthorDate: Wed Jun 16 15:57:29 2021 +0800
Update mvn command in doc (#10834)
* Update NOTICE copyright year to 2021
* Update mvn command in doc
---
docs/community/content/contribute/code-conduct.cn.md | 2 +-
docs/community/content/contribute/code-conduct.en.md | 2 +-
docs/community/content/contribute/release-elasticjob-ui.cn.md | 2 +-
docs/community/content/contribute/release-elasticjob-ui.en.md | 4 ++--
docs/community/content/contribute/release-elasticjob.cn.md | 2 +-
docs/community/content/contribute/release-elasticjob.en.md | 4 ++--
docs/community/content/contribute/release.cn.md | 2 +-
docs/community/content/contribute/release.en.md | 4 ++--
docs/community/content/contribute/release_ui.cn.md | 2 +-
docs/community/content/contribute/release_ui.en.md | 4 ++--
10 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/docs/community/content/contribute/code-conduct.cn.md b/docs/community/content/contribute/code-conduct.cn.md
index 0f64fb3..4981362 100644
--- a/docs/community/content/contribute/code-conduct.cn.md
+++ b/docs/community/content/contribute/code-conduct.cn.md
@@ -18,7 +18,7 @@ chapter = true
## 代码提交行为规范
- - 确保通过全部测试用例，确保执行`./mvnw clean install`可以编译和测试通过。
+ - 确保通过全部测试用例，确保执行 `./mvnw -T 1C clean install` 可以编译和测试通过。
- 确保覆盖率不低于master分支。
- 确保使用Checkstyle检查代码，违反验证规则的需要有特殊理由。模板位置在`https://github.com/apache/shardingsphere/blob/master/src/resources/checkstyle.xml`，请使用checkstyle 8.8运行规则。
- 应尽量将设计精细化拆分；做到小幅度修改，多次数提交，但应保证提交的完整性。
diff --git a/docs/community/content/contribute/code-conduct.en.md b/docs/community/content/contribute/code-conduct.en.md
index 34a5f5b..ba18271 100644
--- a/docs/community/content/contribute/code-conduct.en.md
+++ b/docs/community/content/contribute/code-conduct.en.md
@@ -15,7 +15,7 @@ The following code of conduct is based on full compliance with [ASF CODE OF COND
## Contributor Covenant Submitting of Conduct
- - Make sure all the test cases are passed, Make sure `./mvnw clean install` can be compiled and tested successfully.
+ - Make sure all the test cases are passed, Make sure `./mvnw -T 1C clean install` can be compiled and tested successfully.
- Make sure the test coverage rate is not lower than the master branch.
- Make sure to check codes with Checkstyle. codes that violate check rules should have special reasons. Find checkstyle template from `https://github.com/apache/shardingsphere/blob/master/src/resources/checkstyle.xml`, please use checkstyle `8.8` to run the rules.
- Careful consideration for each `pull request`; Small and frequent `pull request` with complete unit function is welcomed.
diff --git a/docs/community/content/contribute/release-elasticjob-ui.cn.md b/docs/community/content/contribute/release-elasticjob-ui.cn.md
index c5162e1..5f62123 100644
--- a/docs/community/content/contribute/release-elasticjob-ui.cn.md
+++ b/docs/community/content/contribute/release-elasticjob-ui.cn.md
@@ -220,7 +220,7 @@ diff -r apache-shardingsphere-elasticjob-${RELEASE.VERSION}-ui-src shardingspher
- `NOTICE`文件中的年份正确
- 只存在文本文件，不存在二进制文件
- 所有文件的开头都有ASF许可证
-- 能够正确编译，单元测试可以通过 (./mvnw install)
+- 能够正确编译，单元测试可以通过 (./mvnw -T 1C install)
- 检查是否有多余文件或文件夹，例如空文件夹等
**检查二进制包的文件内容**
diff --git a/docs/community/content/contribute/release-elasticjob-ui.en.md b/docs/community/content/contribute/release-elasticjob-ui.en.md
index 8bdc8f2..810a0de 100644
--- a/docs/community/content/contribute/release-elasticjob-ui.en.md
+++ b/docs/community/content/contribute/release-elasticjob-ui.en.md
@@ -224,7 +224,7 @@ diff -r apache-shardingsphere-elasticjob-${RELEASE.VERSION}-ui-src shardingspher
* Correct year in `NOTICE` file
* There is only text files but no binary files
* All source files have ASF headers
-* Codes can be compiled and pass the unit tests (./mvnw install)
+* Codes can be compiled and pass the unit tests (./mvnw -T 1C install)
* Check if there is any extra files or folders, empty folders for example
**Check binary packages**
@@ -236,7 +236,7 @@ to check the following items:
* Correct year in `NOTICE` file
* All text files have ASF headers
* Check the third party dependency license:
- * The software have a compatible license
+ * The software has a compatible license
* All software licenses mentioned in `LICENSE`
* All the third party dependency licenses are under `licenses` folder
* If it depends on Apache license and has a `NOTICE` file, that `NOTICE` file need to be added to `NOTICE` file of the release
diff --git a/docs/community/content/contribute/release-elasticjob.cn.md b/docs/community/content/contribute/release-elasticjob.cn.md
index 8ef40c7..73f7588 100644
--- a/docs/community/content/contribute/release-elasticjob.cn.md
+++ b/docs/community/content/contribute/release-elasticjob.cn.md
@@ -228,7 +228,7 @@ diff -r apache-shardingsphere-elasticjob-${RELEASE.VERSION}-src-release sharding
- `NOTICE`文件中的年份正确
- 只存在文本文件，不存在二进制文件
- 所有文件的开头都有ASF许可证
-- 能够正确编译，单元测试可以通过 (./mvnw install)
+- 能够正确编译，单元测试可以通过 (./mvnw -T 1C install)
- 检查是否有多余文件或文件夹，例如空文件夹等
**检查二进制包的文件内容**
diff --git a/docs/community/content/contribute/release-elasticjob.en.md b/docs/community/content/contribute/release-elasticjob.en.md
index 5e70a8b..1465485 100644
--- a/docs/community/content/contribute/release-elasticjob.en.md
+++ b/docs/community/content/contribute/release-elasticjob.en.md
@@ -230,7 +230,7 @@ diff -r apache-shardingsphere-elasticjob-${RELEASE.VERSION}-src-release sharding
* Correct year in `NOTICE` file
* There is only text files but no binary files
* All source files have ASF headers
-* Codes can be compiled and pass the unit tests (./mvnw install)
+* Codes can be compiled and pass the unit tests (./mvnw -T 1C install)
* Check if there is any extra files or folders, empty folders for example
**Check binary packages**
@@ -243,7 +243,7 @@ to check the following items:
* Correct year in `NOTICE` file
* All text files have ASF headers
* Check the third party dependency license:
- * The software have a compatible license
+ * The software has a compatible license
* All software licenses mentioned in `LICENSE`
* All the third party dependency licenses are under `licenses` folder
* If it depends on Apache license and has a `NOTICE` file, that `NOTICE` file need to be added to `NOTICE` file of the release
diff --git a/docs/community/content/contribute/release.cn.md b/docs/community/content/contribute/release.cn.md
index 53b7b64..24ec6f1 100644
--- a/docs/community/content/contribute/release.cn.md
+++ b/docs/community/content/contribute/release.cn.md
@@ -320,7 +320,7 @@ diff -r apache-shardingsphere-${RELEASE.VERSION}-src-release shardingsphere-${RE
- `NOTICE`文件中的年份正确
- 只存在文本文件，不存在二进制文件
- 所有文件的开头都有ASF许可证
-- 能够正确编译，单元测试可以通过 (./mvnw install)
+- 能够正确编译，单元测试可以通过 (./mvnw -T 1C install)
- 检查是否有多余文件或文件夹，例如空文件夹等
**检查二进制包的文件内容**
diff --git a/docs/community/content/contribute/release.en.md b/docs/community/content/contribute/release.en.md
index 1cf877f..4f6eefe 100644
--- a/docs/community/content/contribute/release.en.md
+++ b/docs/community/content/contribute/release.en.md
@@ -323,7 +323,7 @@ diff -r apache-shardingsphere-${RELEASE.VERSION}-src-release shardingsphere-${RE
* Correct year in `NOTICE` file
* There is only text files but no binary files
* All source files have ASF headers
-* Codes can be compiled and pass the unit tests (./mvnw install)
+* Codes can be compiled and pass the unit tests (./mvnw -T 1C install)
* Check if there is any extra files or folders, empty folders for example
**Check binary packages**
@@ -336,7 +336,7 @@ to check the following items:
* Correct year in `NOTICE` file
* All text files have ASF headers
* Check the third party dependency license:
- * The software have a compatible license
+ * The software has a compatible license
* All software licenses mentioned in `LICENSE`
* All the third party dependency licenses are under `licenses` folder
* If it depends on Apache license and has a `NOTICE` file, that `NOTICE` file need to be added to `NOTICE` file of the release
diff --git a/docs/community/content/contribute/release_ui.cn.md b/docs/community/content/contribute/release_ui.cn.md
index 7354809..ae787ae 100644
--- a/docs/community/content/contribute/release_ui.cn.md
+++ b/docs/community/content/contribute/release_ui.cn.md
@@ -217,7 +217,7 @@ diff -r apache-shardingsphere-${RELEASE.VERSION}-shardingsphere-ui-src shardings
- `NOTICE`文件中的年份正确
- 只存在文本文件，不存在二进制文件
- 所有文件的开头都有ASF许可证
-- 能够正确编译，单元测试可以通过 (./mvnw install)
+- 能够正确编译，单元测试可以通过 (./mvnw -T 1C install)
- 检查是否有多余文件或文件夹，例如空文件夹等
**检查二进制包的文件内容**
diff --git a/docs/community/content/contribute/release_ui.en.md b/docs/community/content/contribute/release_ui.en.md
index 5447154..d8f4bc0 100644
--- a/docs/community/content/contribute/release_ui.en.md
+++ b/docs/community/content/contribute/release_ui.en.md
@@ -218,7 +218,7 @@ diff -r apache-shardingsphere-${RELEASE.VERSION}-shardingsphere-ui-src shardings
* Correct year in `NOTICE` file
* There is only text files but no binary files
* All source files have ASF headers
-* Codes can be compiled and pass the unit tests (./mvnw install)
+* Codes can be compiled and pass the unit tests (./mvnw -T 1C install)
* Check if there is any extra files or folders, empty folders for example
**Check binary packages**
@@ -230,7 +230,7 @@ to check the following items:
* Correct year in `NOTICE` file
* All text files have ASF headers
* Check the third party dependency license:
- * The software have a compatible license
+ * The software has a compatible license
* All software licenses mentioned in `LICENSE`
* All the third party dependency licenses are under `licenses` folder
* If it depends on Apache license and has a `NOTICE` file, that `NOTICE` file need to be added to `NOTICE` file of the release