You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/01/24 04:03:39 UTC
[jira] [Updated] (PHOENIX-1775) [build] implement style checks for
java
[ https://issues.apache.org/jira/browse/PHOENIX-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor updated PHOENIX-1775:
----------------------------------
Summary: [build] implement style checks for java (was: [build] implement style checks for java and python)
> [build] implement style checks for java
> ---------------------------------------
>
> Key: PHOENIX-1775
> URL: https://issues.apache.org/jira/browse/PHOENIX-1775
> Project: Phoenix
> Issue Type: Task
> Reporter: Nick Dimiduk
>
> It would be good to clean up our house a little. Having a uniform codebase helps on boarding new developers, so it would be nice to get something in before the new GSoC folks start really digging into patches.
> [check-style|https://maven.apache.org/plugins/maven-checkstyle-plugin/] is an obvious choice for Java code. There's a maven plugin and plenty of examples of its use. We depend on Python for the users scripts, so we should add a pep8 verification step too. On a quick search I don't see any maven plugins, so an exec step combined with [pytest-pep8|https://pypi.python.org/pypi/pytest-pep8] should do the trick.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)