Mailing-List: contact dev-help@ignite.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.incubator.apache.org
Date: Tue, 11 Aug 2015 22:39:45 +0000 (UTC)
From: =?utf-8?Q?Ra=C3=BAl_Kripalani_=28JIRA=29?= <jira@apache.org>
To: dev@ignite.incubator.apache.org
Message-ID: <JIRA.12855377.1439332743000.38324.1439332785764@Atlassian.JIRA>
In-Reply-To: <JIRA.12855377.1439332743000@Atlassian.JIRA>
References: <JIRA.12855377.1439332743000@Atlassian.JIRA>
 <JIRA.12855377.1439332743278@arcas>
Subject: [jira] [Created] (IGNITE-1236) Create a checkstyle definition and
 hook it into the Maven build
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Ra=C3=BAl Kripalani created IGNITE-1236:
--------------------------------------

             Summary: Create a checkstyle definition and hook it into the M=
aven build
                 Key: IGNITE-1236
                 URL: https://issues.apache.org/jira/browse/IGNITE-1236
             Project: Ignite
          Issue Type: Improvement
          Components: build
            Reporter: Ra=C3=BAl Kripalani
            Assignee: Ra=C3=BAl Kripalani


The community has put together a comprehensive set of coding guidelines her=
e: https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines.

We need a checkstyle definition that we can enforce automatically via the M=
aven Checkstyle plugin.

We can choose to output violations as warnings, or to fail the build if vio=
lations exist. At this point I would prefer the former to avoid "stopping t=
he world". With such a large codebase it is likely that checkstyle violatio=
ns are already present.

This will help contributors adequate their style to the community's standar=
d while they are coding, and will reduce frustration otherwise caused by su=
bmitting pull requests that do not satisfy guidelines, and having to rectif=
y them at a later stage.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)