MethodsOrderCheck contradicts with DeclarationOrder

[denis-konovalyenko]

As far as I understand, the intention of the DeclarationOrder check is to follow the Code Conventions for the Java Programming Language, which state that

These methods should be grouped by functionality rather than by scope or accessibility. For example, a private class method can be in between two public instance methods. The goal is to make reading and understanding the code easier.

At the same time, we have the MethodsOrderCheck which violates this principle and forces to place methods by access level modifiers (please refer to this code for more information).

[0crat]

@krzyk/z please, pay attention to this issue

[0crat]

@denis-konovalyenko/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot!