fix: replace System.out with logger in HelloWorld.java

[sonarqube-agent]

This PR was automatically created by the Remediation Agent's Scheduled backlog remediation feature.

Replaced direct System.out usage with java.util.logging.Logger to fix a code smell violation. Using a proper logger instead of System.out improves code maintainability and allows better control over logging output in production environments.

View Project in SonarCloud

---

Fixed Issues

java:S106 - Replace this use of System.out by a logger. • MAJOR • View issue

Location: src/main/java/hello/HelloWorld.java:8

Why is this an issue?

In software development, logs serve as a record of events within an application, providing crucial insights for debugging. When logging, it is essential to ensure that the logs are:

What changed

Adds the import statement for java.util.logging.Logger, which is required to replace the direct System.out usage with a proper logger. This supports the fix for the code smell where System.out.println was used instead of a dedicated logger.

--- a/src/main/java/hello/HelloWorld.java
+++ b/src/main/java/hello/HelloWorld.java
@@ -2,0 +3,2 @@ package hello;
+import java.util.logging.Logger;
+

Have a suggestion or found an issue? Share your feedback here.

---

SonarQube Remediation Agent uses AI. Check for mistakes.

[sonarqubecloud]

SonarQube reviewer guide

Quality Gate failed

Failed conditions
B Maintainability Rating on New Code (required ≥ A)

🛠️ Remediation Agent ready

• Fix automatically
  Creates a separate PR with fixes for eligible issues

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE