[
https://issues.apache.org/jira/browse/OFBIZ-6270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14508515#comment-14508515 ]
Jacopo Cappellato commented on OFBIZ-6270:
------------------------------------------
I restate that traditionally OFBiz is not strictly following a deprecation workflow.
However when we implement it and we publish releases with deprecation warnings, it is totally acceptable to remove the deprecated code in the next release branch.
> 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)
Locked
