[ https://issues.apache.org/jira/browse/OFBIZ-6270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504656#comment-14504656 ]
Adrian Crum commented on OFBIZ-6270: ------------------------------------ I agree that deprecating things before they are removed is a best practice. At the same time, this particular change was easy to fix in our client code. In most cases it only took a S&R to change package names, and in others the difference was obvious and easy to fix. > base/json/JSON has been removed, with no deprecation window > ----------------------------------------------------------- > > Key: OFBIZ-6270 > URL: https://issues.apache.org/jira/browse/OFBIZ-6270 > Project: OFBiz > Issue Type: Bug > Components: framework > Affects Versions: Trunk, 12.04.04 > Reporter: Adam Heath > Assignee: Adam Heath > Priority: Critical > > The antlr-based json parser(at org.ofbiz.base.json.JSON.cc) was removed last > October(2014-10-27). However, no backwards-compatible class was left in > place, with a proper @Deprecation tag applied. > The proper approach should have been to leave the class in place, adding > @Deprecation, and leaving the json-lib.jar in place. Then, after one > successful release, removing the actual code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)