Plexus-utils replacement

Plexus-utils (see site and javadoc) is used everywhere on Maven but is a legacy component. Most of its features is available using Apache Commons.

Strategy

plexus-utils-commons-bridge is a compatibility layer to ensure backward compatibility, so that we can deprecate plexus-utils.

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.

Update

As we needed a few enhancements and bug fixes for the incremental build support, we moved utility classes we already had in Apache land over to MavenSharedUtils.

Work In Progess

Pick a plexus-utils class, and start creating tests... better still write the tests black box (that's what I am doing!)

Then when you have some tests written in the TCK module, create the implementation class with all the methods:

throw new UnsupportedOperationException( "Not implemented yet!" );

and then you can knock off implementations and see your test pass rate rise in the bridge module.

To stake your claim, commit the test case class first and then (unless you tell us otherwise) you are working on that class!