phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (PHOENIX-1775) [build] implement style checks for java
Date Sun, 24 Jan 2016 03:03:39 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Taylor resolved PHOENIX-1775.
-----------------------------------
    Resolution: Fixed
      Assignee: Nick Dimiduk

Added by Nick, so closing. Please open new JIRA for follow up work.

> [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
>            Assignee: 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)

Mime
View raw message