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" <bimargul...@gmail.com> wrote:
