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

xuehuilang pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/shenyu-website.git


The following commit(s) were added to refs/heads/main by this push:
     new 92393339ed Update blog contains incubator-shenyu changed to 
shenyu(#1039) (#1040)
92393339ed is described below

commit 92393339ed13f5bcf724dd6985092f71ade1a8a8
Author: po-168 <po...@foxmail.com>
AuthorDate: Mon Oct 21 17:56:43 2024 +0800

    Update blog contains incubator-shenyu changed to shenyu(#1039) (#1040)
---
 blog/E2eTest-Analysis.md                                 | 2 +-
 blog/Plugin-SourceCode-Analysis-Dubbo-Plugin.md          | 2 +-
 blog/RegisterCenter-SourceCode-Analysis-Http-Register.md | 6 +++---
 blog/Start-SourceCode-Analysis-Start-Demo.md             | 4 ++--
 4 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/blog/E2eTest-Analysis.md b/blog/E2eTest-Analysis.md
index 117abb9589..62bebec5df 100644
--- a/blog/E2eTest-Analysis.md
+++ b/blog/E2eTest-Analysis.md
@@ -26,7 +26,7 @@ In short, e2e testing is a comprehensive testing method that 
can verify whether
 
 ### How to implement automated e2e testing
 
-In Apache ShenYu, the main steps of e2e testing are reflected in the script of 
the GitHub Action workflow, as shown below, the script is located at 
[~/.github/workflows](https://github.com/apache/incubator-shenyu/tree/master/.github/workflows)
 directory in the e2e file.
+In Apache ShenYu, the main steps of e2e testing are reflected in the script of 
the GitHub Action workflow, as shown below, the script is located at 
[~/.github/workflows](https://github.com/apache/shenyu/tree/master/.github/workflows)
 directory in the e2e file.
 
 ```yaml
 name: e2e
diff --git a/blog/Plugin-SourceCode-Analysis-Dubbo-Plugin.md 
b/blog/Plugin-SourceCode-Analysis-Dubbo-Plugin.md
index a5cc97a894..91fee1521f 100644
--- a/blog/Plugin-SourceCode-Analysis-Dubbo-Plugin.md
+++ b/blog/Plugin-SourceCode-Analysis-Dubbo-Plugin.md
@@ -17,7 +17,7 @@ The `Apache ShenYu` gateway uses the `dubbo` plugin to make 
calls to the `dubbo`
 
 ### 1. Service Registration
 
-Take the example provided on the official website 
[shenyu-examples-dubbo](https://github.com/apache/incubator-shenyu/tree/master/shenyu-examples/shenyu-examples-dubbo/shenyu-examples-apache-dubbo-service).
 Suppose your `dubbo` service is defined as follows (`spring-dubbo.xml`).
+Take the example provided on the official website 
[shenyu-examples-dubbo](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-dubbo/shenyu-examples-apache-dubbo-service).
 Suppose your `dubbo` service is defined as follows (`spring-dubbo.xml`).
 
 ```xml
 <beans xmlns="http://www.springframework.org/schema/beans";
diff --git a/blog/RegisterCenter-SourceCode-Analysis-Http-Register.md 
b/blog/RegisterCenter-SourceCode-Analysis-Http-Register.md
index 1759678b96..f35242c40c 100644
--- a/blog/RegisterCenter-SourceCode-Analysis-Http-Register.md
+++ b/blog/RegisterCenter-SourceCode-Analysis-Http-Register.md
@@ -48,7 +48,7 @@ On the client side, after the data is out of the queue, the 
data is transferred
 
 ### 2. Client Registration Process
 
-When the client starts, it reads the attribute information according to the 
relevant configuration, and then writes it to the queue. Let's take the 
official 
[shenyu-examples-http](https://github.com/apache/incubator-shenyu/tree/master/shenyu-examples/shenyu-examples-http)
 as an example and start the source code analysis . The official example is a 
microservice built by `springboot`. For the configuration of the registration 
center, please refer to the official website [client access conf [...]
+When the client starts, it reads the attribute information according to the 
relevant configuration, and then writes it to the queue. Let's take the 
official 
[shenyu-examples-http](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http)
 as an example and start the source code analysis . The official example is a 
microservice built by `springboot`. For the configuration of the registration 
center, please refer to the official website [client access configuration] [...]
 
 #### 2.1 Load configuration, read properties
 
@@ -221,7 +221,7 @@ Read `username`, `password` and `serverLists` from the 
configuration file, the u
 
 > `SPI`, known as `Service Provider Interface`, is a service provider 
 > discovery feature built into the `JDK`, a mechanism for dynamic replacement 
 > discovery.
 >
-> 
[shenyu-spi](https://github.com/apache/incubator-shenyu/tree/master/shenyu-spi) 
is a custom `SPI` extension implementation for the `Apache ShenYu` gateway, 
designed and implemented with reference to Dubbo [SPI extension 
implementation](https://dubbo.apache.org/zh/docs/v2.7/dev/impls/).
+> [shenyu-spi](https://github.com/apache/shenyu/tree/master/shenyu-spi) is a 
custom `SPI` extension implementation for the `Apache ShenYu` gateway, designed 
and implemented with reference to Dubbo [SPI extension 
implementation](https://dubbo.apache.org/zh/docs/v2.7/dev/impls/).
 
 
 #### 2.3 SpringMvcClientEventListener
@@ -1310,7 +1310,7 @@ public class URIRegisterExecutorSubscriber implements 
ExecutorTypeSubscriber<URI
 - `ShenyuClientRegisterWebSocketServiceImpl`: `Websocket` class,handles 
`Websocket` registration types.
 
 
-From the above, we can see that each microservice has a corresponding 
registration implementation class. The source code analysis in this article is 
based on the official 
[shenyu-examples-http](https://github.com/apache/incubator-shenyu/tree/master/shenyu-examples/shenyu-examples-http)
 as an example, it is of `http` registration type, so the registration 
implementation class for metadata and URI data is 
`ShenyuClientRegisterDivideServiceImpl`: 
`ShenyuClientRegisterDivideServiceImpl`.
+From the above, we can see that each microservice has a corresponding 
registration implementation class. The source code analysis in this article is 
based on the official 
[shenyu-examples-http](https://github.com/apache/shenyu/tree/master/shenyu-examples/shenyu-examples-http)
 as an example, it is of `http` registration type, so the registration 
implementation class for metadata and URI data is 
`ShenyuClientRegisterDivideServiceImpl`: 
`ShenyuClientRegisterDivideServiceImpl`.
 
 - register(): 
 
diff --git a/blog/Start-SourceCode-Analysis-Start-Demo.md 
b/blog/Start-SourceCode-Analysis-Start-Demo.md
index 43f031b099..189c871830 100644
--- a/blog/Start-SourceCode-Analysis-Start-Demo.md
+++ b/blog/Start-SourceCode-Analysis-Start-Demo.md
@@ -19,7 +19,7 @@ tags: [Apache ShenYu]
 Use Git to clone code
 
 ```shell
-git clone https://github.com/apache/incubator-shenyu.git
+git clone https://github.com/apache/shenyu.git
 ```
 
 ### Compile code
@@ -27,7 +27,7 @@ git clone https://github.com/apache/incubator-shenyu.git
 Compile with Maven
 
 ```shell
-cd incubator-shenyu
+cd shenyu
 mvn clean install -Dmaven.javadoc.skip=true -B -Drat.skip=true 
-Djacoco.skip=true -DskipITs -DskipTests
 ```
 

Reply via email to