[
https://issues.apache.org/jira/browse/JSPWIKI-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16615405#comment-16615405
]
ASF subversion and git services commented on JSPWIKI-220:
---------------------------------------------------------
Commit ccdbefa1f39105d31bb3bd18e703d22b1b4c1b98 in jspwiki-site's branch
refs/heads/jbake from [~juanpablo]
[ https://gitbox.apache.org/repos/asf?p=jspwiki-site.git;h=ccdbefa ]
JSPWIKI-220: add title for reports and by default don't ignore missing classes
(it should be activated per execution, when needed
> Binary compatibility test suite
> -------------------------------
>
> Key: JSPWIKI-220
> URL: https://issues.apache.org/jira/browse/JSPWIKI-220
> Project: JSPWiki
> Issue Type: Test
> Components: Core & storage
> Reporter: Janne Jalkanen
> Priority: Minor
> Fix For: 3.0
>
>
> 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)
