camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <christian.muel...@gmail.com>
Subject Re: Removing very old @deprecated code from Apache Camel
Date Mon, 11 May 2015 14:30:09 GMT
+1

Best,
Christian
Am 11.05.2015 04:13 schrieb "Willem Jiang" <willem.jiang@gmail.com>:

> 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.ibsen@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: cibsen@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/
> >
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message