zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "TisonKun (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (ZOOKEEPER-3431) Enable BookKeeper checkstyle configuration
Date Tue, 27 Aug 2019 08:22:00 GMT

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

TisonKun resolved ZOOKEEPER-3431.
---------------------------------
    Resolution: Fixed

We have finished the first pass to enable BookKeeper checkstyle configuration.

Follow up as linked above such as LineLength, Javadoc and name conventions could be separated
topic.

Thus close as we have already reached the point under this issue.

> Enable BookKeeper checkstyle configuration
> ------------------------------------------
>
>                 Key: ZOOKEEPER-3431
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3431
>             Project: ZooKeeper
>          Issue Type: Task
>          Components: build
>            Reporter: maoling
>            Assignee: TisonKun
>            Priority: Major
>             Fix For: 3.6.0
>
>
> As discussed in [mailing list|https://lists.apache.org/thread.html/245557316cbe91e6e189b215eff93c65aac5b5aae355dfe461a84c7b@%3Cdev.zookeeper.apache.org%3E],
our community decide to enable a more meaningful checkstyle configuration, specifically, BookKeeper's
checkstyle configuration.
> Break down implement steps
> 1. Introduce BookKeeper's checkstyle configuration.
> 2. Enable this checkstyle configuration per package, for the first iteration, we want
to enable it in 
>     1). zookeeper-server
>     2). zookeeper-jute
>     3). zookeeper-prometheus-metrics
> UPDATE 2019-08-27:
> x. Turn on checkstyle configuration in project level while suppress on zookeeper-contrib.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message