accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3720) Add apilyzer-maven-plugin to the build to check for API problems
Date Wed, 22 Apr 2015 17:57:58 GMT


Christopher Tubbs commented on ACCUMULO-3720:

Each plugin has its own documentation to link to (for most of those, the URL is documented
in its own pom, as well as searchable in Google), if we do add such documentation.

I don't know how much it's worth it to document the build plugins we're running, because the
reasons for running them tend to be self-evident (e.g. the reasons we're using them is contained
in the description of each), and I can't really think of what documentation would be useful
beyond that and a link to the plugins' own documentation. Is there something beyond those
things which you think might be valuable to put in said documentation?

(BTW, if we were generating/publishing the maven site, a listing of our plugins, with links
to their docs would be auto-generated. For example:

> Add apilyzer-maven-plugin to the build to check for API problems
> ----------------------------------------------------------------
>                 Key: ACCUMULO-3720
>                 URL:
>             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|] 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

View raw message