crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Micah Whitacre (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CRUNCH-427) Utilize clirr-maven-plugin
Date Tue, 24 Jun 2014 02:52:24 GMT

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

Mime
View raw message