Return-Path: X-Original-To: apmail-crunch-dev-archive@www.apache.org Delivered-To: apmail-crunch-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1F94211412 for ; Tue, 24 Jun 2014 02:52:25 +0000 (UTC) Received: (qmail 94045 invoked by uid 500); 24 Jun 2014 02:52:25 -0000 Delivered-To: apmail-crunch-dev-archive@crunch.apache.org Received: (qmail 93996 invoked by uid 500); 24 Jun 2014 02:52:25 -0000 Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@crunch.apache.org Delivered-To: mailing list dev@crunch.apache.org Received: (qmail 93970 invoked by uid 500); 24 Jun 2014 02:52:24 -0000 Delivered-To: apmail-incubator-crunch-dev@incubator.apache.org Received: (qmail 93965 invoked by uid 99); 24 Jun 2014 02:52:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jun 2014 02:52:24 +0000 Date: Tue, 24 Jun 2014 02:52:24 +0000 (UTC) From: "Micah Whitacre (JIRA)" To: crunch-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CRUNCH-427) Utilize clirr-maven-plugin 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/CRUNCH-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041624#comment-14041624 ] Micah Whitacre edited comment on CRUNCH-427 at 6/24/14 2:52 AM: ---------------------------------------------------------------- It should only be reporting issues on "public" API.[1] So changes to private and package classes and methods should be reported as "WARN" or "INFO". I'm not finding any blanket policy to change it to globally exclude protected so we'd have to either restrict which classes/packages are included and or which exceptions we want to include. I'm not sure we'd want to globally exclude protected anyways as we'd want to know about incompatibilities on classes like DoFn. [1] - http://clirr.sourceforge.net/clirr-core/exegesis.html was (Author: mkwhitacre): It should only be reporting issues on "public" API.[1] So changes to private and package classes and methods should be reported as "WARN" or "INFO". [1] - http://clirr.sourceforge.net/clirr-core/exegesis.html > Utilize clirr-maven-plugin > -------------------------- > > Key: CRUNCH-427 > URL: https://issues.apache.org/jira/browse/CRUNCH-427 > Project: Crunch > Issue Type: Wish > Reporter: Allan Shoup > Priority: Minor > Attachments: CRUNCH-427.patch > > > To prevent issues like CRUNCH-426, the [clirr-maven-plugin|http://mojo.codehaus.org/clirr-maven-plugin] could be used to identify potential passivity issues between versions. -- This message was sent by Atlassian JIRA (v6.2#6252)