You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Bob Harner (JIRA)" <ji...@apache.org> on 2017/01/16 14:09:26 UTC

[jira] [Resolved] (TAP5-2569) ClientBehaviorSupport deprecation documentation

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

Bob Harner resolved TAP5-2569.
------------------------------
    Resolution: Fixed
      Assignee: Bob Harner

Sorry for the trouble. Yes, not the best deprecation process there. The release notes have been updated.

http://tapestry.apache.org/release-notes-54.html

> ClientBehaviorSupport deprecation documentation
> -----------------------------------------------
>
>                 Key: TAP5-2569
>                 URL: https://issues.apache.org/jira/browse/TAP5-2569
>             Project: Tapestry 5
>          Issue Type: Documentation
>          Components: tapestry-core
>    Affects Versions: 5.4, 5.4.1
>            Reporter: MihkelJ
>            Assignee: Bob Harner
>            Priority: Minor
>
> ClientBehaviorSupport was removed in 5.4 with no replacement. The deprecation was done in a way that maintains binary compatibility, but replaces most of the implementation with UnsupportedOperationExceptions. 
> Being that this client-facing service was not deprecated in 5.3.8 and before, this constitutes a breaking change, which does not seem to be reflected anywhere in the documentation. 
> The most notable omission is in the release notes.



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