[jira] [Comment Edited] (ACCUMULO-3720) Add apilyzer-maven-plugin to the build to check for API problems

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ACCUMULO-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14490179#comment-14490179 ] 

Christopher Tubbs edited comment on ACCUMULO-3720 at 4/10/15 7:19 PM:
----------------------------------------------------------------------

A rough draft of what this would look like is available [in my branch on GitHub|https://github.com/ctubbsii/accumulo/tree/apilyzer]. It currently will fail the build, and is dependent on outstanding work [~kturner] is doing for the parent issue (ACCUMULO-3657), so I expect the exact ruleset to change before merging to master.


was (Author: ctubbsii):
A rough draft of what this would look like is available in my branch on GitHub. It currently will fail the build, and is dependent on outstanding work [~kturner] is doing for the parent issue (ACCUMULO-3657), so I expect the exact ruleset to change before merging to master.

> Add apilyzer-maven-plugin to the build to check for API problems
> ----------------------------------------------------------------
>
>                 Key: ACCUMULO-3720
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3720
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: build
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>             Fix For: 1.7.0
>
>
> [apilyzer-maven-plugin|http://apilyzer.revelc.net/analyze-mojo.html] has just been released, and can check for the kinds of API problems described in ACCUMULO-3657. We should configure it to run by default in the build, at the very least to create the report, if not to fail the build when it finds an unexpected problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)