You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by "Juan Pablo Santos Rodríguez (JIRA)" <ji...@apache.org> on 2018/09/14 21:36:00 UTC

[jira] [Resolved] (JSPWIKI-220) Binary compatibility test suite

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

Juan Pablo Santos Rodríguez resolved JSPWIKI-220.
-------------------------------------------------
       Resolution: Fixed
         Assignee: Juan Pablo Santos Rodríguez
    Fix Version/s:     (was: 3.0)
                   2.11.0-M1

added a binary compatibilty report to the site generation. When releasing 2.11.0-M1, {{plugin.japicmp.jspwiki-new}} on pom.xml file of jbake branch should be updated accordingly.

Also, new modules appearing should be added to that pom.xml too. For 2.10 <-> 2.11, they should check against 2.10's jspwiki-war

> Binary compatibility test suite
> -------------------------------
>
>                 Key: JSPWIKI-220
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-220
>             Project: JSPWiki
>          Issue Type: Test
>          Components: Core &amp; storage
>            Reporter: Janne Jalkanen
>            Assignee: Juan Pablo Santos Rodríguez
>            Priority: Minor
>             Fix For: 2.11.0-M1
>
>
> It would be very good to have a binary compatibility test suite - essentially a pre-compiled JAR file with JUnit tests - that would make sure that our binary API does not change from release to release.
> I think this would be good to take aboard in 3.0 (though earlier is possible), because we'll be breaking the binary compatibility in 3.0 anyway... It would also be a good starting point for a new, improved JSPWiki API.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)