Kogito-8084 Sonarcloud - Addressing code smells related to anonymous inner classes, lambda syntax and incorrectly accessed static members

[kbowers-ibm]

https://issues.redhat.com/browse/KOGITO-8084

Goal here is to reduce the number of code smells in Kogito-runtimes.

Addressed in this PR are the following code smells:

1. (Java) "static" members should be accessed statically (4):

https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS2209&id=org.kie.kogito%3Akogito-runtimes
I have addressed this by changing the instance-reference to a static-reference

2. (Java) Lambdas containing only one statement should not nest this statement in a block (14):

https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS1602&id=org.kie.kogito%3Akogito-runtimes
I have addressed this by removing useless curly braces around the afffected statements.

3. (Java) Anonymous inner classes containing only one method should become lambdas (13):

https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS1604&id=org.kie.kogito%3Akogito-runtimes
I have addressed this by replacing anonymous inner classes with lambdas

4. (Java) Parentheses should be removed from a single lambda input parameter when its type is inferred (8):

https://sonarcloud.io/project/issues?resolved=false&rules=java%3AS1611&id=org.kie.kogito%3Akogito-runtimes
I have addressed this by removing unnecessary parentheses.

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.

build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

• for pull request checks
  Please add comment: Jenkins retest this

• for a specific pull request check
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] tests

• for quarkus branch checks
  Run checks against Quarkus current used branch
  Please add comment: Jenkins run quarkus-branch

• for a quarkus branch specific check
  Run checks against Quarkus current used branch
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-branch

• for quarkus main checks
  Run checks against Quarkus main branch
  Please add comment: Jenkins run quarkus-main

• for a specific quarkus main check
  Run checks against Quarkus main branch
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-main

• for quarkus lts checks
  Run checks against Quarkus lts branch
  Please add comment: Jenkins run quarkus-lts

• for a specific quarkus lts check
  Run checks against Quarkus lts branch
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-lts

• for native checks
  Run native checks
  Please add comment: Jenkins run native

• for a specific native check
  Run native checks
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] native

• for mandrel checks
  Run native checks against Mandrel image
  Please add comment: Jenkins run mandrel

• for a specific mandrel check
  Run native checks against Mandrel image
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] mandrel

• for mandrel lts checks
  Run native checks against Mandrel image and quarkus lts branch
  Please add comment: Jenkins run mandrel-lts

• for a specific mandrel lts check
  Run native checks against Mandrel image and quarkus lts branch
  Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] mandrel-lts

• Full Kogito testing (with cloud images and operator BDD testing)
  Please add comment: Jenkins run BDD
  This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...

[sonarcloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

64.0% Coverage
0.0% Duplication

[baldimir]

Hi @kbowers-ibm, @elguardian, is this still relevant please? If yes, could you please rebase with the latest changes from main?