fix: rename local variable to prevent field shadowing

[sonarqube-agent]

Renamed local variable 'compilerArgs' to 'resolvedCompilerArgs' to eliminate variable shadowing of the class field. This resolves a MAJOR SonarQube issue and improves code clarity by ensuring variable names don't hide outer scope declarations.

View Project in SonarCloud

---

Fixed Issues

java:S1117 - Rename "compilerArgs" which hides the field declared at line 63. • MAJOR • View issue

Location: core/src/main/java/com/webcohesion/enunciate/Enunciate.java:639

Why is this an issue?

Shadowing occurs when a local variable has the same name as a variable or a field in an outer scope.

What changed

Renames the local variable 'compilerArgs' to 'resolvedCompilerArgs' at line 639, which was shadowing the class field 'compilerArgs' declared at line 63. This directly resolves the variable shadowing code smell by giving the local variable a unique name that no longer hides the outer field.

--- a/core/src/main/java/com/webcohesion/enunciate/Enunciate.java
+++ b/core/src/main/java/com/webcohesion/enunciate/Enunciate.java
@@ -639,3 +639,3 @@ public class Enunciate implements Runnable {
-      List<String> compilerArgs = getCompilerArgs();
-      getLogger().debug("Compiler args: %s", compilerArgs);
-      options.addAll(compilerArgs);
+      List<String> resolvedCompilerArgs = getCompilerArgs();
+      getLogger().debug("Compiler args: %s", resolvedCompilerArgs);
+      options.addAll(resolvedCompilerArgs);

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 passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud