Getting an error while sonar scan for code coverage parameter

[Vinutham18]

Hi Team,
While running the sonar scan for ESQL file with plugin 3.5.0 version , we are getting below error which result is no code coverage analysis

[INFO] 07:18:18.228 Sensor IaC Docker Sensor [iac] (done) | time=8ms
[INFO] 07:18:18.266 Sensor ESQL Squid Sensor [iibesql]
[WARNING] 07:18:18.266 ESQL sensor execute
[INFO] 07:18:18.268 5 source files to be analyzed
[ERROR] 07:18:18.324 Unable to analyse file:
java.lang.UnsupportedOperationException: Unknown metric: complexity_in_functions
at org.sonar.scanner.sensor.DefaultSensorStorage.saveMeasure(DefaultSensorStorage.java:175)
at org.sonar.scanner.sensor.DefaultSensorStorage.store(DefaultSensorStorage.java:147)
at org.sonar.api.batch.sensor.measure.internal.DefaultMeasure.doSave(DefaultMeasure.java:96)
at org.sonar.api.batch.sensor.internal.DefaultStorable.save(DefaultStorable.java:45)

Could you please look into the issue.

[Vinutham18]

Could you please update on this above one any resolution

[campbellcopeland]

It appears that ‘complexity_in_functions’ and some other deprecated metrics have now been removed for latest SonarQube (as of version 9 I think) - not sure if this project is still maintained, but you could fork it and update the code/recompile & deploy for your needs? Or feed the solution back into this repo? Or revert to an older SonarQube version if an option?

[Vinutham18]

Can't we do do anything on esql plugin code to bring up to date for sonar qube version 9

[Vinutham18]

Please check for your reference, Could you please go through this and please check something can be done from your end

The COMPLEXITY_IN_FUNCTIONS metric was deprecated and removed from SonarQube due to a broader cleanup of outdated complexity metrics that began as early as SonarQube version 6.7 and culminated in their full removal in SonarQube 25.1.0.102122. [github.com]

Why Was It Deprecated?
Redundancy and Obsolescence:
Metrics like complexity_in_functions, function_complexity, and file_complexity_distribution were considered redundant or less meaningful compared to newer metrics like Cognitive Complexity, which provides a more accurate measure of code understandability.
Shift to Cognitive Complexity:
SonarQube has shifted focus to Cognitive Complexity, which better reflects how difficult code is to understand, rather than just counting control structures like loops and conditionals. [stackoverflow.com]
Plugin and API Simplification:
Removing deprecated metrics helps simplify the plugin API and reduces maintenance overhead. It also avoids confusion for users who might rely on outdated metrics that no longer align with SonarQube’s analysis philosophy. [docs.sonarsource.com]
Breaking Changes in New Versions:
These metrics were officially removed in SonarQube 25.1, and any plugin still referencing them (like the ESQL plugin) will throw errors unless updated to remove or replace those references. [github.com]
What Should You Do?
If you're maintaining or using a plugin like the ESQL plugin:
Remove references to COMPLEXITY_IN_FUNCTIONS and similar deprecated metrics.
Switch to Cognitive Complexity if you need a complexity-related metric.
Ensure compatibility with SonarQube 25.1+ by checking the SonarQube deprecation notes. [docs.sonarsource.com]

Using Cognitive Complexity in SonarQube is a powerful way to assess how difficult your code is to understand, which directly impacts maintainability and team productivity. Here's a breakdown of how to use it effectively:
🧠 What Is Cognitive Complexity?
Cognitive Complexity measures how hard it is for a human to read and understand code. Unlike Cyclomatic Complexity, which counts the number of paths through code, Cognitive Complexity focuses on how code structure affects readability.
It increases when:
Control flow is interrupted (e.g., if, for, while, switch)
Nesting levels increase
Logical branches are added It does not increase for constructs that improve clarity (e.g., guard clauses, early returns). [neurolaunch.com], [sonarsource.com]
🛠 How to Use It in SonarQube

1. Enable Cognitive Complexity Rules
   SonarQube includes Cognitive Complexity rules by default in most language profiles (Java, JavaScript, TypeScript, etc.). You can:
   Go to Project > Issues > Rules
   Filter by Cognitive Complexity
   Review flagged methods/functions
2. Set Thresholds
   SonarQube typically flags methods with Cognitive Complexity > 15. You can customize this in your quality profile:
   Navigate to Quality Profiles
   Edit the rule for Cognitive Complexity
   Adjust the threshold based on your team's tolerance
3. Use It for Refactoring Decisions
   High Cognitive Complexity indicates code that may be:
   Hard to maintain
   Prone to bugs
   Difficult to onboard new developers
   Use it to identify hotspots for refactoring. For example:
   Break large methods into smaller ones
   Reduce nesting
   Simplify logic
4. Track Over Time
   In SonarQube dashboards, you can monitor Cognitive Complexity trends across releases. This helps ensure your codebase remains maintainable as it grows.
   📉 Tips to Reduce Cognitive Complexity
   Avoid deep nesting: Flatten logic where possible.
   Use early returns: They reduce nesting and improve clarity.
   Split complex methods: Break them into smaller, focused functions.
   Use descriptive names: Clear naming reduces mental load.
   Refactor conditionals: Replace complex if-else chains with polymorphism or strategy patterns.

[Vinutham18]

@campbellcopeland : Please review and approve this changes cnescatlab/sonar-cnes-report#430

[Vinutham18]

@campbellcopeland : How do you contact to merge things to EXXETA , Could you please help me on this,its been a while are struggling

[Mythaluswolf]

@Vinutham18 Hi, I saw you were able to fix the issue, thank you! How were you able to recompile the project? what did you use exactly? since I had a fix as well and was not able to compile it using mvn clean install.