Hi! If those methods are already deprecated, then I'd say we should drop them now.
Most times those methods didn't got deprecated because they are 'unpretty' but because they are seriously flawed. Like missing encoding parameter, missing timezone, not multithreading capable, etc. So if those methods are deprecated for more than a year now (or < maven-2.2.1 and maven-3.0), then I'd say lets drop them now. LieGrue, strub --- On Mon, 6/13/11, Stephen Connolly <[email protected]> wrote: > From: Stephen Connolly <[email protected]> > Subject: Re: Truly awful code in plexus... > To: "Maven Developers List" <[email protected]> > Date: Monday, June 13, 2011, 5:55 AM > if we knew the provenance of the > plexus code, yes... but we don't > > - 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 13 Jun 2011 00:12, "Benson Margulies" <[email protected]> > wrote: > > 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] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
