Sounds like Dani and John sees adding @Deprecated as the correct approach. Thanks for the clarification. Adding them is also very simple with the clean up procedure described here: http://wiki.eclipse.org/Generify_A_Java_Project
Thanks, Lars 2013/7/16 John Arthorne <[email protected]> > If someone is compiling against our binaries without source won't they > only see a warning if the annotation is used? Within the IDE this is an > edge case because most people will have access to the source, but I can > imagine production builds would only compile against our platform runtime > binaries and the deprecation warning would not appear. > > John > > > > From: Markus Keller <[email protected]> > To: E4 Project developer mailing list <[email protected]>, > Date: 07/15/2013 04:36 PM > Subject: Re: [e4-dev] Question about @Deprecate > Sent by: [email protected] > ------------------------------ > > > > I see no point in adding @Deprecated and I would not use it. > > Currently, it just clutters code, since the @deprecated Javadoc tag is > still required (must explain the transition path to the replacement API or > why there is no replacement). If Java compilers ever stop processing > @deprecated, then the "Add missing '@Deprecated' annotations" clean up can > be used. > > Here's a Stackoverflow entry: * > http://stackoverflow.com/questions/5039723/should-i-use-javadoc-deprecation-or-the-annotation-in-java > *<http://stackoverflow.com/questions/5039723/should-i-use-javadoc-deprecation-or-the-annotation-in-java> > Nobody found a use case that would require @Deprecated right now. > > Markus > > > > From: Daniel Megert/Zurich/IBM@IBMCH > To: E4 Project developer mailing list <[email protected]> > Date: 2013-07-15 13:51 > Subject: Re: [e4-dev] Question about @Deprecate > Sent by: [email protected] > ------------------------------ > > > > > For the plug-ins that have moved to Java 1.5 would it add value to add > the @Deprecated annotation? > > Yes, adding a @Deprecated annotation is the way to go in 1.5 an beyond. > For details see * > ** > http://docs.oracle.com/javase/1.5.0/docs/guide/javadoc/deprecation/deprecation.html > *<http://docs.oracle.com/javase/1.5.0/docs/guide/javadoc/deprecation/deprecation.html> > > Dani > > > From: Lars Vogel <[email protected]> > To: E4 Project developer mailing list <[email protected]> > Date: 12.07.2013 12:18 > Subject: [e4-dev] Question about @Deprecate > Sent by: [email protected] > ------------------------------ > > > > Hi, > > I see in sometimes in the Eclipse platform source code that only the > @deprecated Javadoc annotation is used. > > For the plug-ins that have moved to Java 1.5 would it add value to add the > @Deprecated annotation? > > Best regards, Lars > > > > _______________________________________________ > e4-dev mailing list > [email protected]* > **https://dev.eclipse.org/mailman/listinfo/e4-dev*<https://dev.eclipse.org/mailman/listinfo/e4-dev> > _______________________________________________ > e4-dev mailing list > [email protected]* > **https://dev.eclipse.org/mailman/listinfo/e4-dev*<https://dev.eclipse.org/mailman/listinfo/e4-dev> > _______________________________________________ > e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/e4-dev > > > _______________________________________________ > e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/e4-dev > >
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
