Hi all,
It was a slow week in the Community this time. Looks like folks haven’t shaken off their food comas 
yet. 
Nonetheless, like every week, we’d like to take a moment to recognize you, the users, who help improve the ecosystem for everyone by sparking valuable discussions and providing feedback that drives continuous improvement in our products.
SonarQube for IDE:
- SonarQube for Visual Studio is locking the
Web.configfile. Turns out we’re not releasing our file handles like we should. Doh! Thanks @BartNucor. SLCORE-1870
SonarQube Server / SonarQube Community Build:
- @Scott was trying to build SonarQube Community Build from source, but got stuck on some missing closed-source dependencies. Sorry about that. It should be fixed soon.
Rules & Languages Improvements:
-
@alexgwolff nicely summarized the situation in a long-running thread about
tsarchitecture:S7197, arguing that cyclic dependencies are relevant only in the implementation, but fine for API declarations. We’re not fully on board (yet?) but we’ve added a ticket to the backlog to come back to this later. -
java:S4488told @pshem to switch his class annotation from@RequestMappingto@GetMapping. The only problem is that you can’t do that with classes. SONARJAVA-5908
-
javaS2095tells you to usetry-with-resourcesif the resource is created directly, but not if you use a library to do it. This is probably a deliberately-chosen trade-off to keep from raising false-positive issues when the library manages the resource itself. Nonetheless, we’re going to keep an eye on this. Thanks @narendran.a! JAVASE-152
Thank you again to everyone mentioned—and to those we may have missed—for your ongoing contributions in making this community stronger and helping us improve Sonar products.
If you’d like to give a shout-out to someone, whether a community member or a SonarSourcer who helped you, please do so below. And if there’s someone you think we should acknowledge next week, let us know!