Strictly speaking we should only remove deprecated code in the next
major release.
For functionality that is not used a lot I think we can make an
exemption though.
It is still important then that we list all removed functions in the
release notes so people are aware of it.
Christian
On 10.05.2015 09:56, Claus Ibsen wrote:
Hi
Over the time we have marked methods as @deprecated such as when the
method had a spelling mistake or for other reasons. We usually said in
the javadoc that the method is to be removed in the future or Camel 3
or in a few releases etc.
Though we often really haven't removed them.
I wonder if we should not walk through camel-core and other important
modules and remove deprecated that has been there for many years.
Today I spot code that has been deprecated for 5 and 6 years.
Any thoughts?
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
