[jboss-jira] [JBoss JIRA] (ELY-1523) Update the JAPICMP settings so that we only detect changes that break API compatibility

[Jan Kalina (JIRA)]

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

Jan Kalina commented on ELY-1523:
---------------------------------

Problem is {{breakBuildBasedOnSemanticVersioning}} parameter, which sets allowed changes by version numbers:
Because newVersion is 1.2.1.Final and oldVersion is 1.2.1.SP1 (all three parts of the version are same), japicmp requires level UNCHANGED, which mean any change in classes breaks build.
This also mean, that if newVersion and oldVersion would have different major version, it would allow API breaking changes!

Going to set checked level manually, independent on version names.

> Update the JAPICMP settings so that we only detect changes that break API compatibility
> ---------------------------------------------------------------------------------------
>
>                 Key: ELY-1523
>                 URL: https://issues.jboss.org/browse/ELY-1523
>             Project: WildFly Elytron
>          Issue Type: Task
>          Components: Build
>            Reporter: Farah Juma
>            Assignee: Jan Kalina
>
> Currently, the JAPICMP settings will result in a build failure if new public API has been added. As we will be tagging .Final releases more regularly, we need to be able to allow new public API into a patch release so we should only be detecting changes that break API compatibility not changes that add new public API.  
> As an example, try building the 1.2.1.Final tag (https://github.com/wildfly-security/wildfly-elytron/tree/1.2.1.Final). The build will fail due to new public API unless the -DskipCompatibility flag is passed in.



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