[jboss-jira] [JBoss JIRA] (ELY-1398) Verify public API signatures during build.

[Darran Lofthouse (JIRA)]

    [ https://issues.jboss.org/browse/ELY-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477633#comment-13477633 ] 

Darran Lofthouse commented on ELY-1398:
---------------------------------------

Some other options mentioned in HipChat

[3:24 PM] Tomaz Cerar: other tool i know about is https://lvc.github.io/japi-compliance-checker/
[3:24 PM] Tomaz Cerar: but it doesn't have any maven plugins
[3:25 PM] Tomaz Cerar: you can get nice reports
[3:25 PM] Tomaz Cerar: https://abi-laboratory.pro/java/tracker/compat_report/slf4j/1.5.11/1.6.0/c87de/bin_compat_report.htm...
[3:25 PM] Tomaz Cerar: but it is much more manual work

[3:27 PM] Tomaz Cerar: there is some comercial tooling
[3:27 PM] Tomaz Cerar: but they come with *lots* more stuff
[3:28 PM] Tomaz Cerar: so just BAPI diff is rarely avalible as standalone tool
[3:31 PM] Tomaz Cerar: @DarranLofthouse JT harness (from openjdk toolkit) also has signature check
[3:31 PM] Tomaz Cerar: https://wiki.openjdk.java.net/display/CodeTools/JT+Harness
[3:32 PM] Tomaz Cerar: https://wiki.openjdk.java.net/display/CodeTools/sigtest

> Verify public API signatures during build.
> ------------------------------------------
>
>                 Key: ELY-1398
>                 URL: https://issues.jboss.org/browse/ELY-1398
>             Project: WildFly Elytron
>          Issue Type: Enhancement
>          Components: Build
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>             Fix For: 1.1.6.CR1, 1.2.0.Beta7
>
>
> This task will involve adding the ability to generate a signature for a specific version and verify them during the build - we only want this to apply to packages identified as public API.
> Animal Sniffer seems a good candidate http://www.mojohaus.org/animal-sniffer/
> Generation of a signature we can likely make on-demand as we only really need that at the point we tag a release.
> We would definitely want checking to run for CI PR processing but can decide if all builds should be checking with an option to disable or all disabled with an option to enable.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)