You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamás Cservenák (Jira)" <ji...@apache.org> on 2022/02/16 08:57:00 UTC
[jira] [Created] (MNGSITE-480) IDE Codestyle vs Maven Checkstyle: a bossfight
Tamás Cservenák created MNGSITE-480:
---------------------------------------
Summary: IDE Codestyle vs Maven Checkstyle: a bossfight
Key: MNGSITE-480
URL: https://issues.apache.org/jira/browse/MNGSITE-480
Project: Maven Project Web Site
Issue Type: Bug
Reporter: Tamás Cservenák
Codestyle updated in MNGSITE-465 for Idea has discrepancies wrt checkstyle plugin rules.
Typical example:
IDEA IDE reformat result:
{noformat}
StreamSupport.stream( iteratorSearchResponse.iterator().spliterator(), false )
.sorted( ArtifactInfo.VERSION_COMPARATOR ).forEach( ai -> {
artifactInfos.add( ai );
page.add( convert( ai, null ) );
} );
{noformat}
But, checktyle:
{noformat}
[ERROR] src/main/java/org/apache/maven/index/search/backend/indexer/internal/IndexerCoreSearchBackendImpl.java:[127,83] (blocks) LeftCurly: '{' at column 83 should be on a new line.{noformat}
In short, for me it looks like our checkstyle is too rigid, unprepared for Java 8 lambdas? (as IMHO the code snippet above with curly on next line would look awkward).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)