jean pierre Lerbscher

Ok let's go for a complete reformatting. I'm not familiar with spotless so I'll leave it to you. But the most important thing is to keep the commits readable.

No commit will be merged between this https://github.com/javaparser/javaparser/pull/4409 and the complete reformatting. So let me know when you're ready to proceed.

Thank you for your contributions. You can close this issue if you think it's finished.

Thank you for your reply. We're going to migrate the Javaparser project to another distribution.

We have also noticed that Indepth can also quickly correct the 105 violations of the rule "Collection.isEmpty() should be used to test for emptiness" as well as a large number...

We also noticed that you had 60 violations of rule [S2129] Constructors should not be used to instantiate 'String', 'BigInteger', 'BigDecimal' and primitive-wrapper classes. This fix eliminates the need to...

You also have 151 violations of rule [S1148] Throwable.printStackTrace(...) should never be called. https://www.indepth.fr/documentation.html#BooleanChecksShouldNotBeInvertedRule

You also have 60 violations of the rule [S1130] "throws" declarations should not be superfluous https://www.indepth.fr/documentation.html#ThrowsDeclarationsShouldNotBeSuperfluousRule

You can also improve the readability of some methods by applying the following patches which correct the Sonar RSPEC-2692 violation "Checking if a value is included in a String or...

It's a custom playbook, I'm going to try become: True. Thanks