[rocketmq] branch 5.0.0-beta updated: Fix check style to paas CI

[jinrongtong]

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

jinrongtong pushed a commit to branch 5.0.0-beta
in repository https://gitbox.apache.org/repos/asf/rocketmq.git


The following commit(s) were added to refs/heads/5.0.0-beta by this push:
     new 48e2e2d4b Fix check style to paas CI
48e2e2d4b is described below

commit 48e2e2d4b7c6a7757071cf874c51ca61f1116e9d
Author: rongtong.jrt <rongtong....@alibaba-inc.com>
AuthorDate: Fri Apr 29 16:51:42 2022 +0800

    Fix check style to paas CI
---
 .../rocketmq/apis/consumer/MessageListener.java    | 38 ++++++++++------------
 1 file changed, 18 insertions(+), 20 deletions(-)

diff --git 
a/apis/src/main/java/org/apache/rocketmq/apis/consumer/MessageListener.java 
b/apis/src/main/java/org/apache/rocketmq/apis/consumer/MessageListener.java
index bcfab9748..a56e67781 100644
--- a/apis/src/main/java/org/apache/rocketmq/apis/consumer/MessageListener.java
+++ b/apis/src/main/java/org/apache/rocketmq/apis/consumer/MessageListener.java
@@ -24,33 +24,31 @@ import org.apache.rocketmq.apis.message.MessageView;
  * synchronously.
  *
  * <p>PushConsumer will fetch messages from brokers and dispatch them to an
- * embedded thread pool in form of <code>Runnable</code> tasks to achieve
- * desirable processing concurrency.
+ * embedded thread pool in form of <code>Runnable</code> tasks to achieve 
desirable processing concurrency.
  *
  * <p>Refer to {@link PushConsumer} for more further specs.
  *
  * <p>
- *     <strong>Thread Safety</strong>
- *     This class may be called concurrently by multiple threads. 
Implementation should be thread safe.
+ * <strong>Thread Safety</strong>
+ * This class may be called concurrently by multiple threads. Implementation 
should be thread safe.
  * </p>
  */
 public interface MessageListener {
 
-  /**
-   * Callback interface to handle incoming messages.
-   *
-   * Application developers are expected to implement this interface to fulfill
-   * business requirements through processing <code>message</code> and return
-   * <code>ConsumeResult</code> accordingly.
-   *
-   * PushConsumer will, on behalf of its group, acknowledge the message to
-   * broker on success; In case of failure or unexpected exceptions
-   * were raised, it will negatively acknowledge <code>message</code>, which
-   * would potentially get re-delivered after the configured back off period.
-   *
-   * @param message The message passed to the listener.
-   * @return {@link ConsumeResult#SUCCESS} if <code>message</code> is properly 
processed; {@link ConsumeResult#FAILURE}
-   *         otherwise.
-   */
+    /**
+     * Callback interface to handle incoming messages.
+     *
+     * Application developers are expected to implement this interface to 
fulfill business requirements through
+     * processing <code>message</code> and return
+     * <code>ConsumeResult</code> accordingly.
+     *
+     * PushConsumer will, on behalf of its group, acknowledge the message to 
broker on success; In case of failure or
+     * unexpected exceptions were raised, it will negatively acknowledge 
<code>message</code>, which would potentially
+     * get re-delivered after the configured back off period.
+     *
+     * @param message The message passed to the listener.
+     * @return {@link ConsumeResult#SUCCESS} if <code>message</code> is 
properly processed; {@link
+     * ConsumeResult#FAILURE} otherwise.
+     */
     ConsumeResult onMessage(MessageView message);
 }