You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2016/04/28 18:41:12 UTC

[jira] [Updated] (WSS-577) Binary compatibility broken between version <=2.1.3 and >=2.1.4 with org.apache.wss4j.dom.WSSecurityEngineResult

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

Colm O hEigeartaigh updated WSS-577:
------------------------------------
    Fix Version/s: 2.1.6

> Binary compatibility broken between version <=2.1.3 and >=2.1.4 with org.apache.wss4j.dom.WSSecurityEngineResult
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: WSS-577
>                 URL: https://issues.apache.org/jira/browse/WSS-577
>             Project: WSS4J
>          Issue Type: Bug
>    Affects Versions: 2.1.4, 2.1.5
>            Reporter: Gary Gregory
>            Assignee: Colm O hEigeartaigh
>             Fix For: 2.1.6
>
>
> Binary compatibility is broken between version 2.1.3 and low and 2.1.4 and greater:
> - <= 2.1.3 with {{org.apache.wss4j.dom.WSSecurityEngineResult}}
> - >= 2.1.4 with {{org.apache.wss4j.dom.engine.WSSecurityEngineResult}}
> Welcome to my jar hell :-(
> Please do not move public classes around in a minor release!
> Feel free to move public types in a major release if you also rename the package and Maven coordinates.
> I'm not sure what can be done here aside from the brute force fix of adding a copy of the class to the old package.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org