yes, that is exactly the goal. E.g. instead of imlementing our own Base64 stuff we will either shade in parts or delegate over to commons-io.
After the initial switch from p-u to m-s-u we will review all code and make a major upgrade and drop obsolete parts. LieGrue, strub ----- Original Message ----- > From: Aleksandar Kurtakov <[email protected]> > To: Maven Developers List <[email protected]>; Mark Struberg > <[email protected]> > Cc: > Sent: Thursday, August 30, 2012 11:07 AM > Subject: Re: Any maven-shared or maven-core release pending? > > > > ----- Original Message ----- >> From: "Mark Struberg" <[email protected]> >> To: "Maven Dev" <[email protected]> >> Sent: Thursday, August 30, 2012 11:55:13 AM >> Subject: Any maven-shared or maven-core release pending? >> >> Hi folks! >> >> Is there any maven-core or maven-shared release pending? >> I'd like to start with moving all maven stuff from plexus-utils to >> maven-shared-utils. >> >> The reason is simple: >> 1.) It always got argued that we cannot just replace plexus-utils >> because we don't know how many plugins are using it. And people >> feared about side effects which could harm stability. >> As we do this now in a whole new module with a new package name we >> can really easily upgrade that stuff to proper 2012 style and don't >> need to keep em 2005ish anymore ;) >> >> 2.) For implementing the incremental build stuff I need a few classes >> extended, and the only way we can guarantee this to be reliably >> available is to host this stuff in maven itself (where it was >> originally hosted btw - 80% of the plexus utils code is a fork of >> old ant/jakarta/commons stuff). And since the codehaus repo got >> closed down silently I have no confidence in that stuff anymore. >> > Can we hope that stuff that belongs to Apache commons will be used from there > or > contributed back instead of growing yet another utility library that > duplicates > commons-[io|lang|codec|beanutils|..]? > Java land is already full of such util libraries serving same purposes but > with > different problems and bugs, so let's try to not do it again. > > Regards, > Alexander Kurtakov > Red Hat Eclipse Team > > >> >> I locally already upgraded a few maven-shared libs without any >> problems. I think we can get this done in 1 week + another week of >> cleaning up the obsolete code as Kristian proposed in the other >> mail. >> >> Wdyt? When may I start with the transition? >> >> LieGrue, >> strub >> >> >> --------------------------------------------------------------------- >> 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]
