commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charles Honton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COMMONSSITE-89) Support both clirr and japicmp
Date Tue, 26 Jul 2016 02:29:20 GMT

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

Charles Honton commented on COMMONSSITE-89:
-------------------------------------------

Commits 1754062/1754063 adds two new profiles: clirr and japicmp

clirr profile is activated by presence of src/site/resources/profile.clirr file.  This profile
will add the clirr report to the site.  (Clirr does not support java 7 or 8)

japicmp is activated by presence of src/site/resources/profile.japicmp file.  This profile
will add the japicmp report to the site.  Additionally, during the verify phase, the japicmp
plugin will fail build on any binary incompatibility.

Pom parent Version 41 requires adopters to explicitly enable clirr report.  To get the clirr
report which was previously on by default, you must either activate the clirr profile with
a -P command line parameter or add the src/site/resources/profile.clirr file.


> Support both clirr and japicmp
> ------------------------------
>
>                 Key: COMMONSSITE-89
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-89
>             Project: Commons All
>          Issue Type: Improvement
>          Components: Commons Parent Pom
>            Reporter: Charles Honton
>
> Allow older projects to continue with clirr report.  Allow newer projects to adopt japicmp
report.  Those projects which adopt japicmp will fail build if binary compatibility change
is detected.



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

Mime
View raw message