On Thu, Oct 14, 2010 at 8:43 PM, Daniel Kulp <dk...@apache.org> wrote: > > Anyone else find it funny to see a comment like: >
No not really. The important thing is to mark it as @deprecated to discourage people to use it, when we plan to remove it. We may have been a bit aggressive saying that X is going to be removed in Y release. I wonder if we should lay back a bit on this and say eg Camel 3.0. However in this case its a util class which most likely is not used by end users at all. So I bet is safe to remove it even for Camel 2.5. > /** > * A helper class for working with times in various units > * > * @version $Revision$ > * @deprecated will be removed in Camel 2.5 > */ > @Deprecated > > in a file that is still there mere hours before (or maybe after) Camel 2.5 is > supposed to be released? > > :-) > > > -- > Daniel Kulp > dk...@apache.org > http://dankulp.com/blog > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
