Martijn Kruithof wrote: > Hi > > I have started marking every @deprecated in our code with since tags. > > (And removing @deprecated items introduced in 1.7, so things > introduced in 1.7 and already markted deprecated) > > For instance changed > > * @deprecated Use getGlobalFilterSet().addFilter(token,value) > to > * @deprecated since 1.4.x Use getGlobalFilterSet().addFilter(token,value) > > Is this seen as useful. Yes, this is useful if we do enforce a policy of removing stuff which has been deprecated across 2 or 3 major releases. You might want to test to see how the generated javadoc looks like with these texts. > > And how do you look at the proposal to drop the deprecated since 1.4.x > in 1.7? > I am not sure. I do not know which concrete methods are deprecated since 1.4x. I think that a list of what would concretely go away plus a vote would be necessary. I was previously working for a large European software company. When we upgraded from Ant 1.4 to Ant 1.6, there was only one API incompatiblitity which we had to solve. Because we still used Ant 1.4 to build old releases of our applications, we had to build one adapter for the class (I think it was Zip or ZipOutputStream) where the signature of a method had changed. > Would it be ok to start dropping items deprecated in 1.5.x and 1.6.x > in 1.8? > Do not know either. > Martijn > Antoine
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
