Java 23 rules not working

SonarQube for IDE IntelliJ Platform
, ,
1

Hello! I’m on SonarQube for IDE: IntelliJ version 10.27.1.81796 and for this code:

    /// Infers the log level from the given message.
    ///
    /// @param message the message
    /// @return the inferred log level
    public static Level inferLevel(String message) {

I still get these java:S1176 issues:

  • Document the parameter(s): message
  • Document this method return value

Is this a bug or am I missing something? I already have sonar.java.source = 23 set. Thanks!

SonarQube for IDE: IntelliJ 10.23 - Java 23 support and new Java and Pyspark rules
2

Another example:

/// The abstract class for any Vaadin [CustomResource].
///
/// @param <S> the type of the spec
/// @param <T> the type of the status
@AdditionalPrinterColumn(
        name = "AGE",
        type = AdditionalPrinterColumn.Type.DATE,
        jsonPath = ".metadata.creationTimestamp")
public abstract class VaadinResource<S, T> extends CustomResource<S, T> {

Raises java:S1176:

  • Document the parameter(s): <S>, <T>
3

Hey @heruan, I’ve moved your messages to a dedicated thread so we can better track and troubleshoot the issues you’re experiencing.

To get started, could you please share your SonarQube for IDE logs when running an analysis on the files where the issues are still being reported?

You can find instructions on how to retrieve the logs here.

Thanks!

1 Like
4

Hey @nicolas.quinquenel thanks for creating this thread! These are the logs from the plugin Logs tab: SonarQube for IDE logs · GitHub

And these are the issues detected:

Screen Shot 2025-07-23 at 12.01.17 PM
Screen Shot 2025-07-23 at 12.01.17 PM717×363 50.2 KB

I couldn’t fine the “Enable the Analysis logs and Verbose output in the tool window settings” option mentioned in the documentation link, I hope what’s in that tab is enough.

Thanks!

6

Hey @nicolas.quinquenel can I help further to get this fixed?

7

Apologies for the delay in our response—we want to assure you that your question hasn’t been forgotten.

I’ve tagged our Java expert to take a closer look, and you should expect an answer as soon as possible.

Thank you for your patience!

9

To give an update, we worked on a fix thanks to your feedback. This will be included in one of our next releases, thank you!

11

Thanks for the update! I see the PR has been merged a week ago, and yesterday there’s been a new release of the IntelliJ plugin, but unfortunately it seems the fix is not included yet.

12

The Java analyzer version that includes the fix has not yet been released, sorry for the inconvenience. Supposedly, our next version of SonarQube for IntelliJ should contain the fix, and it will be released in approximately 2 weeks.

1 Like
13

@nicolas.quinquenel any estimation for a Sonar Java release? I’ve seen recent IntelliJ Plugin releases, but latest fixes are still not there. Thanks!

14

You can track the releases from our sonar-java analyzer here. Unfortunately, it seems that they haven’t yet released a new version. I will ping them on this thread and see if they can give you a better estimate. Thank you for your patience.

1 Like
17

Thanks, I’ll keep an eye on that page. Is there a roadmap with planned/missing issues for next release, to make an idea of what’s holding it? A rough estimation would help us set internal deadlines to restore our Quality Profile for the project. I’d be happy to contribute if that helps!

18

Hello Giovanni.

Just to mention that we recently merged the changes to main branch on the analyzer side, and they will be potentially shipped on the next SQS and SQC versions soon.

20

Hey @heruan, the latest version of SonarQube for IDE includes the new Java analyzer version. Could you please verify that everything is working as expected now? Thanks!

1 Like