[
https://issues.apache.org/jira/browse/MCHECKSTYLE-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16323173#comment-16323173
]
Sylwester Lachiewicz commented on MCHECKSTYLE-279:
--------------------------------------------------
Is it necessary to use Maven's own checkstyle rules that that differ
significantly from other large Java projects?
Maybe is worth to review this rules and try to apply best from standard
checkstyle templates (like google_style) or adopt something based on Spring's
style?
Unfortunately Intellij no longer supports all of Maven code style rules (like
space before/after call argument) and trying to align to this rules take
significant amount of time that can be used to support other issues.
Sample:
https://github.com/checkstyle/checkstyle/blob/master/src/main/resources/google_checks.xml
https://github.com/spring-projects/spring-boot/blob/master/spring-boot-project/spring-boot-parent/src/checkstyle/checkstyle.xml
> mark ParameterNumber, MethodLength and FileLength rules as warning only
> -----------------------------------------------------------------------
>
> Key: MCHECKSTYLE-279
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-279
> Project: Maven Checkstyle Plugin
> Issue Type: Task
> Components: predefined ruleset: Maven
> Affects Versions: 2.13
> Reporter: Hervé Boutemy
>
> These rules by default cause an error: Maven parent pom marks them as "ignore
> violation", since we don't really enforce refactoring when limits are hit
> Perhpas it would be better to just mark these rules as warning: it's the way
> we use them
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
