+1 for StAX as well. But first steps first :) I do of course agree that we should keep xpp3 so far. Even if this has the downside that we still need to ship the old plexus-utils in maven-core.
LieGrue, strub ----- Original Message ----- > From: Hervé BOUTEMY <[email protected]> > To: Maven Developers List <[email protected]> > Cc: > Sent: Thursday, August 30, 2012 1:48 PM > Subject: Re: Any maven-shared or maven-core release pending? > > I like it > > we should probably set a dependencyManagement in maven parent pom to > streamline library version. > > Notice that this rewrite with package change will do the job for most parts > of > plexus-utils but not for Xpp3, since this one has objects created in Maven > core that get manipulated by plugins: we absolutely need binary compatibility > here. > Or finally find a way to replace XPP3 by StAX, like dreamt a long time ago... > [1] > > > Regards, > > Hervé > > [1] > https://cwiki.apache.org/confluence/display/MAVENOLD/Use+StAX+instead+of+XPP3 > > Le jeudi 30 août 2012 09:55:13 Mark Struberg a écrit : >> 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. >> >> >> 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
