As some of you may have noticed, I have not been accepting patches or changes to the versions maven plugin for quite a while now.
The blocker has been that there is one and only one machine that I can trust to tell me that the integration tests pass and there are no regressions introduced. That machine is an Acer Aspire One running Fedora Core 14 and is still in good health, but I have not been happy with having a single point of failure... So my plan has always been to re-work the integration tests so that they can work on any machine, and then once portable integration tests are in place, then restart development... Hence the https://svn.codehaus.org/mojo/trunk/sandbox/mock-repository-maven-plugin project Half way through writing that, however, I found that the arch I had picked was no-good... Well I have finally had a chance to put some cycles against a better arch... https://svn.codehaus.org/mojo/trunk/sandbox/mrm I am much happier with this architecture, it's still not quite ready yet... but already it is good enough that I can get all but 2 of the integration tests for v-m-p to pass using Maven 2.0.11 and the two failing tests are failing because the behaviour is not what it should be... i.e. true failures not unexpected errors. On Maven 2.2.1 there are 3 failing tests (all look to be real failures) and on Maven 3.0.3 we have 12 failing tests all of which look to be real failures. So, the short story is, versions-maven-plugin should start getting some love in the near future... the mrm-maven-plugin (mock repository manager) should allow the love to be given, and is very near the point where it is _done_. Once mrm is done, and promoted out of sandbox, the next task is to fix those failing tests.... only after that will the issue backlog be resolved. My aim is to cut a release that fixes all the failing tests and has one new feature (display-dependency-updates should pay attention to the required minimum version of maven for the plugin updates) That release will be the last release that works on the 2.0.x version of Maven... (the extra feature is so that people using v-m-p on 2.0.x will not try and upgrade to a version they cannot use) Then there will be one release that works on 2.2.x After that you will need Maven 3.x -Stephen --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
