accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-1636) Use Clirr maven plugin to enforce API compatibility
Date Wed, 30 Oct 2013 22:58:25 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

John Vines updated ACCUMULO-1636:
---------------------------------


This sounds really cool. I'm torn as to whether or not this is okay to fix in 1.6 post feature
freeze, since it's not code but development. However, last rleease things bottle necked a
bit of really late revisions to the maven build process.

> Use Clirr maven plugin to enforce API compatibility
> ---------------------------------------------------
>
>                 Key: ACCUMULO-1636
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1636
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: build
>            Reporter: Christopher Tubbs
>             Fix For: 1.6.0
>
>
> Clirr can check for API compatibility.
> There's a useful plugin for maven to run it: http://mojo.codehaus.org/clirr-maven-plugin/check-mojo.html
> We might be able to use this to enforce API compatibility for things we want to remain
stable (for instance, by failing the build if an incompatible change is detected).



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message