Here are the comments from the JIRA ticket (edited for relevance)
Bill van Melle added a comment - 28/Jul/11 22:29 Although this was the logical change to make, I hope that somebody is recording this somewhere as a prominent backward-incompatible change in the next release. Anybody who has written an executeFailed method and done something as innocuous as saying Exception fault = task.getFault(); will have to edit their code for it to run under 2.0.1 (as I have had to do just now when I updated to the latest trunk). Chris Bartlett added a comment - 28/Jul/11 23:04 A valid point, and one that the release process does take care of as far as I am aware. The JIRA tickets that are resolved and included in each release are listed in the release notes. Pivot 2.0 release notes are available here http://pivot.apache.org/download.cgi#2.0 While the Pivot API is evolving, changes are generally not made without reason, and without the opportunity for discussion. Bill van Melle added a comment - 28/Jul/11 23:55 I'm aware of the automatic generation of release notes, which is great. But as a consumer of release notes, and trying to answer the question "should I upgrade?", I would love there to be a section called something like "Incompatible changes". Somebody by hand created something like that for 2.0 (https://cwiki.apache.org/confluence/display/PIVOT/Major+Feature+Changes+Between+1.5.x+and+2.0). Most of that page discusses features, but you also learn important things like that WTKXSerializer was renamed and the Shape classes were removed. Changing Exception to Throwable in one API isn't nearly that big, but it would be nice if there were a way to somehow flag it for the benefit of code migrators, so that you wouldn't have to click on every single JIRA link to discover that one of them, only listed as "A Task's TaskListener will not be called if a Throwable is thown...", implies that you might have to edit your Task code.
