Github, generate report for Indentation/all-examples-in-one

Report for Indentation/all-examples-in-one:
https://checkstyle-diff-reports.s3.us-east-2.amazonaws.com/7aef136e9e656faa46d1e6f758b1d696c8603bc4_2025010028/reports/diff/index.html

@0utplay,
Can you help us validate that this fix actually covers all your problems.

To build jar from this PR, please read #17135 (comment)

Thanks s lot in advance

The fix is not done, I still need to do some work. I'll do it ASAP

Hi, just give me another ping and I will test it :)

Github, generate report for Indentation/all-examples-in-one

Report for Indentation/all-examples-in-one:
https://checkstyle-diff-reports.s3.us-east-2.amazonaws.com/02c5b3ca6b3eecc1dbb34e6c796b38ab740e9b0e_2025234041/reports/diff/index.html

Fix is ready for testing.
@0utplay could you please validate that the fix covers all your problems. Thanks!

@Aziz-755 , can you check behavior on trinodb
#17163 (comment)
Looks like we have access to their sources, and it is them reporting this issue initially.

We can add their codebase to our CI, no leak problems happening again, and no special reports required to trigger

Fix is ready for testing. @0utplay could you please validate that the fix covers all your problems. Thanks!

Hi, I just tried all of our previous failures. These are now fixed. I could not validate that no new issues arose as we are using the gradle checkstyle plugin.

@Aziz-755 , can you check behavior on trinodb #17163 (comment) Looks like we have access to their sources, and it is them reporting this issue initially.

We can add their codebase to our CI, no leak problems happening again, and no special reports required to trigger

I have checked the behavior on the reported file and the false positives are gone.

If testing checkstyle on the whole project is needed could you please share a guide how can I run checkstyle on a project ? ( I am only familiar with a single file 😅 )

Example for other projects
57962fa

Version override looks like possible at
https://github.com/trinodb/trino/blob/b4b2d9a3d285efca71298acea8f181d775b964bd/pom.xml#L190

I tested the changes on the TrinoDB project. I ran Checkstyle 10.25.0 (before the changes) and Checkstyle 10.25.1-SNAPSHOT-all (after the changes) using the following two commands:

D:\Working on Checkstyle>java -jar checkstyle-10.25.1-SNAPSHOT-all.jar -c config.xml trino\ > outputUsing-checkstyle-10.25.1-SNAPSHOT-all

D:\Working on Checkstyle>java -jar checkstyle-10.25.0-all.jar -c config.xml trino\ > outputUsing-checkstyle-10.25.0-all

outputUsing-checkstyle-10.25.0-all.txt
outputUsing-checkstyle-10.25.1-SNAPSHOT-all.txt

You can find the output files attached. All false positives related to this issue have been removed. I also noticed the presence of other violations related to switch statements, and in my opinion, they are valid.