Hi Bertrand, > On 12 Nov 2019, at 12:22, Bertrand Delacretaz <[email protected]> wrote: > > > Also, I think the transition to a stricter style guide needs to be > clearly defined. I'm *not* in favor of reformatting "everything" as > that blurs the much more important diffs about actual code changes. My > preference would be to leave existing code as is and only reformat > when source code files are extensively rewritten or created.
Another option would be to configure the maven-checkstyle-plugin [0] in the parent pom and let individual modules slowly implement the coding style once they update to a newer parent. With this we’d make sure that the style doesn’t change according to the used IDE and also that the style is enforced and consistent across all modules. Thanks, Radu (wearing conference t-shirts in case people here want to throw tomatoes at me for the above suggestion) [0] - https://maven.apache.org/plugins/maven-checkstyle-plugin/ <https://maven.apache.org/plugins/maven-checkstyle-plugin/>
