Since Checkstyle 10.17.0
Rationale: Grouping constructors together in a class improves code readability and maintainability. It allows developers to easily understand the different ways an object can be instantiated and the tasks performed by each constructor.
To configure the check:
<module name="Checker"> <module name="TreeWalker"> <module name="ConstructorsDeclarationGrouping"/> </module> </module>
Example of correct grouping of constructors:
public class Example1 { int x; Example1() {} Example1(String s) {} // comments between constructors are allowed. Example1(int x) {} Example1(String s, int x) {} void foo() {} private enum ExampleEnum { ONE, TWO, THREE; ExampleEnum() {} ExampleEnum(int x) {} ExampleEnum(String s) {} int x = 10; void foo() {} } }
Example of incorrect grouping of constructors:
public class Example2 { int x; Example2() {} Example2(String s){} void foo() {} Example2(int x) {} // violation 'Constructors should be grouped together' Example2(String s, int x) {} // violation 'Constructors should be grouped together' private enum ExampleEnum { ONE, TWO, THREE; ExampleEnum() {} ExampleEnum(int x) {} final int x = 10; ExampleEnum(String str) {} // violation 'Constructors should be grouped together' void foo() {} } Example2(float f) {} // violation 'Constructors should be grouped together' }
All messages can be customized if the default message doesn't suit you. Please see the documentation to learn how to.
com.puppycrawl.tools.checkstyle.checks.coding