[jboss-jira] [JBoss JIRA] (ELY-1572) japicmp force source compatibility, but only binary compatibility is required

[Jan Kalina (JIRA)]

     [ https://issues.jboss.org/browse/ELY-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Kalina updated ELY-1572:
----------------------------
    Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/1145  (was: https://github.com/wildfly-security/wildfly-elytron/pull/1134)


> japicmp force source compatibility, but only binary compatibility is required
> -----------------------------------------------------------------------------
>
>                 Key: ELY-1572
>                 URL: https://issues.jboss.org/browse/ELY-1572
>             Project: WildFly Elytron
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.3.0.Final
>            Reporter: Jan Kalina
>            Assignee: Jan Kalina
>             Fix For: 1.4.0.CR1
>
>
> As part of ELY-1523 japicmp was configured to force binary and source compatibility.
> By last discussion, only binary compatibility is required.
> {panel}
> *Honza Kalina*	jaspicmp reports it as source incompatibility, not as binary incompatibility - so it maybe it is false positive, as I would say it should be source-compatible...
> *Darran Lofthouse*	Binary is the only one we are really interested in, i.e. will an update to a later version of Elytron break something.  Most of our backwards compatibility strategy is more about breaking things and upsetting people
> {panel}
> Japicmp currently reports adding default method into interface as source incompatible change (see  https://github.com/siom79/japicmp/issues/201) -> blocks adding IV into MaskedPassword in ELY-867



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