[
https://issues.apache.org/jira/browse/OFBIZ-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507425#comment-14507425
]
Martin Becker commented on OFBIZ-6273:
--------------------------------------
There are about 375 findings of "Deprecated" keyword in java code in the trunk,
some are duplicated, because of the deprecated keyword in javaDoc and as
annotation for the same method.
What about to link this issue with [OFBIZ-6275] "OFBiz code seems make use of
other deprecated OFBiz features" from Adam for which a branch already exists,
since the use of some deprecated API by OFBiz has to be changed first before we
can get rid of the deprecated API itself?
I would vote for first fixing the findings from Adam and then removing the
deprecated API, either in the branch Adam just created or in another branch in
sequence.
Another question is: What about deprecated fields/entities and corresponding
upgrade services?
> Remove from trunk the deprecated code if deprecated before December 2014
> ------------------------------------------------------------------------
>
> Key: OFBIZ-6273
> URL: https://issues.apache.org/jira/browse/OFBIZ-6273
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
> Affects Versions: Trunk
> Reporter: Jacopo Cappellato
>
> The code that has been deprecated before December 2014 will be released in
> the releases of the 14.12 branch: in this way users will be notified about
> deprecated methods/code.
> For this reason we can proceed and remove all the deprecated code from trunk,
> deprecated before December 2014.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
