accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3720) Add apilyzer-maven-plugin to the build to check for API problems
Date Wed, 22 Apr 2015 17:39:00 GMT

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

Josh Elser commented on ACCUMULO-3720:
--------------------------------------

Great, thanks for writing this up. I'm sure I'll be back to reference it.

It sems like we're collecting a nice suite of automated tools that can be run at build time
to help enforce good code at commit rather than release (findbugs, checkstyle, RAT, apilyzer).
Tangential, it may be good to think about a developers section on the user manual to cover
these (what do they do, what are failure conditions, how do you fix them, etc).

> 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
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> [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)

Mime
View raw message