[camel] branch main updated: fix the checkstyle violation

[bvahdat]

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

bvahdat pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new 3bc3c10998d fix the checkstyle violation
3bc3c10998d is described below

commit 3bc3c10998d8bc226087831b7d2167fa1267dda7
Author: Babak Vahdat <bvah...@apache.org>
AuthorDate: Sun Dec 18 15:21:36 2022 +0100

    fix the checkstyle violation
---
 .../camel/itest/sql/FromJmsToJdbcIdempotentConsumerToJmsTest.java     | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git 
a/tests/camel-itest/src/test/java/org/apache/camel/itest/sql/FromJmsToJdbcIdempotentConsumerToJmsTest.java
 
b/tests/camel-itest/src/test/java/org/apache/camel/itest/sql/FromJmsToJdbcIdempotentConsumerToJmsTest.java
index 92333d86f47..7915cb5359b 100644
--- 
a/tests/camel-itest/src/test/java/org/apache/camel/itest/sql/FromJmsToJdbcIdempotentConsumerToJmsTest.java
+++ 
b/tests/camel-itest/src/test/java/org/apache/camel/itest/sql/FromJmsToJdbcIdempotentConsumerToJmsTest.java
@@ -47,7 +47,7 @@ import static org.junit.jupiter.api.Assertions.assertTrue;
 public class FromJmsToJdbcIdempotentConsumerToJmsTest extends 
CamelSpringTestSupport {
 
     // this logger is used both by this class as well as 
FromJmsToJdbcIdempotentConsumerToJmsXaTest, so why not static
-    private final Logger LOG = LoggerFactory.getLogger(this.getClass());
+    private final Logger logger = LoggerFactory.getLogger(this.getClass());
 
     private JdbcTemplate jdbcTemplate;
 
@@ -188,7 +188,7 @@ public class FromJmsToJdbcIdempotentConsumerToJmsTest 
extends CamelSpringTestSup
                     alreadyErrorThrown = true;
                     throw new ConnectException("Forced cannot send to AMQ 
queue");
                 } else {
-                    LOG.info("Now successfully recovered from the error and 
can connect to AMQ queue");
+                    logger.info("Now successfully recovered from the error and 
can connect to AMQ queue");
                 }
             }
         });