Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 56EECCFEA for ; Thu, 20 Nov 2014 14:44:34 +0000 (UTC) Received: (qmail 22377 invoked by uid 500); 20 Nov 2014 14:44:34 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 22262 invoked by uid 500); 20 Nov 2014 14:44:34 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 21957 invoked by uid 99); 20 Nov 2014 14:44:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Nov 2014 14:44:33 +0000 Date: Thu, 20 Nov 2014 14:44:33 +0000 (UTC) From: "Sean Busbey (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-12525) Wrap lines longer than 100 chars MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-12525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219435#comment-14219435 ] Sean Busbey commented on HBASE-12525: ------------------------------------- {quote} bq. My concern is that there are so many warnings from checkstyle we can do the same thing we have for javadoc now, where we set the current number of errors and we show only the diff in the result. You want enforce that the new stuff is correct. (it is almost the same thing as the deprecated api.. you enforce the new way, but you keep the old bad stuff to avoid breaking everyone who can't migrate) {quote} We do this now. However the numbers involved are in the multiple-thousands and "what's 2 more when there are 2500?" Also this doesn't help for when the contributor wants to know what they've added. For the javadoc it's pretty easy to just run through the javadoc goal because the baseline is 2 expected javadoc warnings. {quote} bq. Would your concern be mitigated if I also brought the fix back to branch-1? earlier branches? assuming that everyone can rebase up to this patch... yes it will help. but if you are stuck in an old branch and you want to backport stuff this is just extra work and it will be increasingly painful as more as you differ from the original branch. {quote} Just to make sure I'm clear, this is specifically a concern for people maintaining forks outside of the project repo? > Wrap lines longer than 100 chars > -------------------------------- > > Key: HBASE-12525 > URL: https://issues.apache.org/jira/browse/HBASE-12525 > Project: HBase > Issue Type: Sub-task > Reporter: Sean Busbey > Assignee: Sean Busbey > Priority: Minor > Labels: checkstyle > > After broadening the acceptable long lines in HBASE-12523, we still end up with ~900 cases of lines over our chosen length. > Go through and wrap all of those that are sensible to wrap and then update HBASE-12523 with a list of additional exclusions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)