If we want to keep the broken behavior of these already @Deprecated classes, then I'd think we'd just copy them wholesale from plexus to the bridge. There's no advantage in replacing an old broken version with a new broken, and they're already deprecated, and the right thing to do to callers is to make them use modern methods.
On Sun, Jun 12, 2011 at 6:33 PM, Stephen Connolly <[email protected]> wrote: > thanks > > - Stephen > > --- > Sent from my Android phone, so random spelling mistakes, random nonsense > words and other nonsense are a direct result of using swype to type on the > screen > On 12 Jun 2011 23:25, "Hervé BOUTEMY" <[email protected]> wrote: >> strategy added in the proposal [1], for future reference >> >> Regards, >> >> Hervé >> >> [1] > https://cwiki.apache.org/confluence/display/MAVEN/Plexus-utils+replacement >> >> Le lundi 13 juin 2011, Stephen Connolly a écrit : >>> here is my thoughts, for first release we need to have a drop in >>> replacement that works exactly the same as the original... that gives us > a >>> way to kill the old version (otherwise people will just say, "I'm not >>> going to fix my code when it works fine with plexus utils... ok maybe > I'll >>> fix it later") >>> >>> we will mark every method and class in the bridge as deprecated, but we >>> need the recommendations for each replacement to put in the deprecated >>> tags. >>> >>> for the second release we flip the @reproducesplexusbug rule and fix all >>> those test cases >>> >>> for the third release, everything is deprecated >>> >>> - Stephen >>> >>> --- >>> Sent from my Android phone, so random spelling mistakes, random nonsense >>> words and other nonsense are a direct result of using swype to type on > the >>> screen >>> On 12 Jun 2011 21:24, "Benson Margulies" <[email protected]> wrote: >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
