SonarCloud remove candidate rule: java:S135 Loops should not contain more than a single "break" or "continue" statement

[CDellaGiusta]

This poll closes Friday, April 18th 2025.

Candidate rule for removal: java:S135
Number of issues with this rule in Uyuni: 17
Rule: Loops should not contain more than a single "break" or "continue" statement
Software qualities impacted: MAINTAINABILITY
Why is this an issue:

The use of break and continue statements increases the complexity of the control flow and makes it harder to understand the program logic. In order to keep a good program structure, they should not be applied more than once per loop.

This rule reports an issue when there is more than one break or continue statement in a loop. The code should be refactored to increase readability if there is more than one.

Should it be removed?:
There may be more than one break or continue statement if early loop quitting is necessary.

All rule issues in Uyuni: https://sonarcloud.io/project/issues?languages=java&issueStatuses=OPEN%2CCONFIRMED&id=uyuni-project_uyuni&rules=java%3AS135

Examples in our code:

private static int findColon ( int start, StringBuilder query){
          boolean inQuotes = false;
          for (int i = start; i < query.length(); i++) {
              char c = query.charAt(i);
              if (c == '"' || c == '\'') {
                  inQuotes = !inQuotes;
              }

              if (inQuotes) {
                  continue;
              }

              if (c == ':' && (query.charAt(i + 1) == ':')) {
                  i++;
                  continue;
              }
          }






   .....
    for (Method methodIn : methods) {
          if (methodIn.getName().equals(methodCalled)) {
              foundMethod = methodIn;
              Class[] types = foundMethod.getParameterTypes();
              if (types.length != params.length) {
                  continue;
              }
              break;
          }
      }

      if (found) {
          rightMethod = found;
          break;
      }
  }
}

[cbosdo]

It usually is described as a bad coding practice to abuse "goto"-like instructions. But I fear keeping this rule would require risky and long refactorings