On Feb 4, 2008, at 10:41 AM, Sergiu Dumitriu wrote: > +5 > > Also, in the deprecated methods we should log the calls, if possible > capturing where exactly that code is used. This will ease the code > upgrade, as velocity is not that easy to refactor when you don't get > compilation errors.
yes, very good idea. -Vincent > Vincent Massol wrote: >> Hi, >> >> I'd like us to agree on using the strategy described here: >> http://blogs.sonatype.com/john/2007/11/09/1194630418546.html >> >> This has several advantages: >> >> 1) Keeps our code clean >> 2) Put all backward compatibility code in a single place which makes >> it easy too to remove when the time has come >> >> Here's my +1 >> >> If we agree I'll do a try of using this approach for moving out the >> deprecated methods in the XWiki class into an aspect. It should be a >> piece of cake since we already have the aspectj plugin in place for >> the core build. >> >> Thanks >> -Vincent _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
