Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: added replacement strategy as explained in http://markmail.org/search/?q=list%3Aorg.apache.maven.dev#query:list%3Aorg.apache.maven.dev+page:1+mid:jbudiafopquwh55e+state:results

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.

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!)

...