BTW We might also think about cleaning old "Available since Camel 2.x"
notes from the documentation. IMHO We should keep information only about
the updates for the version of Camel we still support. That is 2.13 or
higher. Who cares that Camel 2.8 provides some "new" feature? ;)

pon., 11.05.2015 o 12:13 użytkownik Henryk Konsek <hekon...@gmail.com>
napisał:

> Hi,
>
> I think that if we mark something as deprecated in 2.x, then we can safely
> remove it in 2.(x + 1). Just need to be sure that the deprecation
> information was available in the documentation between 2.x and 2.(x + 1)
> period. And that we have provided some valid usage alternative for the
> users.
>
> Cheers.
>
> pon., 11.05.2015 o 04:13 użytkownik Willem Jiang <willem.ji...@gmail.com>
> napisał:
>
>> We can update the code in Camel 2.15.x branch to warn the user the API
>> could be removed in Camel 2.16.0 first, then we can clean up the quite old
>> API.
>>
>> There are some APIs just marked with @deprecated but we don’t have any
>> other alternative options for the user to choice. I think we need to clean
>> up these deprecated APIs at the same time.
>>
>> --
>> Willem Jiang
>>
>> Red Hat, Inc.
>> Web: http://www.redhat.com
>> Blog: http://willemjiang.blogspot.com (English)
>> http://jnn.iteye.com (Chinese)
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>>
>>
>>
>> On May 10, 2015 at 3:57:23 PM, Claus Ibsen (claus.ib...@gmail.com) 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?
>> >
>> >
>> > --
>> > Claus Ibsen
>> > -----------------
>> > Red Hat, Inc.
>> > Email: cib...@redhat.com
>> > Twitter: davsclaus
>> > Blog: http://davsclaus.com
>> > Author of Camel in Action: http://www.manning.com/ibsen
>> > hawtio: http://hawt.io/
>> > fabric8: http://fabric8.io/
>> >
>>
>>

Reply via email to