Hi all,
Checking in from Sydney, where we had a fantastic time at the SonarQube World Tour yesterday! It’s always rewarding to meet people in person—especially those who say, “I think you helped me on the Community once!” ![]()
As always, we want to highlight those who spark valuable discussions and provide feedback that drives continuous improvement.
SonarQube Server & SonarQube Community Build:
-
Special thanks to @jcervantes-sipecom for creating guides to help users set up Microsoft Entra SSO with Nginx and HAProxy!
-
We’ll be enhancing the logging for importing JaCoCo reports thanks to @MarekZajicek, who identified a confusing issue. JACOCO-34
SonarQube for IDE:
- @jasonhuang971, @Morten_Hattesen, and @apupier all reported
ArrayIndexOutOfBoundsExceptionerrors in git blame processing. We’ve opened SLCORE-1544 to address this—thank you for your detailed reports and stack traces!
Rule & Language Improvements:
-
@Ginkgo and @dukedagmor discussed
csharpsquid:S6562flagging date-onlyDateTimeconstructors. Based on their input, we updated the documentation to suggest usingDateOnlyfor .NET 6+ projects. Thank you for your feedback! -
@jayasuryat and @Florian_Fournier requested that rule kotlin:S107 exclude
@Composablefunctions, noting these functions often require many parameters by design. The team will either add an exception or provide a separate threshold for them. Thanks for raising this framework-specific pattern! -
@aikebah reported both false positives and negatives in
java:S2259when using Apache Commons validators, since the rule doesn’t differentiate betweenGenericValidator.isBlankOrNullandStringUtils.isBlank’s null-handling. SONARJAVA-5704 was created to improve the rule’s logic. Excellent analysis! -
@sithmein discovered a false positive in
java:S2259, where generic types are incorrectly flagged as nullable if only their type parameters are annotated with@Nullable. A ticket was opened to address this—thanks for the clear examples!
Thanks again to everyone mentioned—and those we may have missed—for your continued contributions to strengthening this community and helping us improve Sonar products.
If you’d like to shout out someone—a fellow community member or a SonarSourcer who helped you—please share below. And if there’s someone you think we should recognize next week, let us know!