A new lifecycle phase 'process-test-classes' was introduced in maven-2.0.5, but hudson doesn't trigger
the plugin goals associated with the phase, even when it is running on newer version of maven.
I attached the test-harness pom.xml and it outputs 'process-test-classes phase was invoked.' on stand-
alone maven, while it doesn't show up in hudson log.
I believe it is caused by the fact that Hudson embeds maven-2.0.4, and components.xml used to inject
interceptors remained old and doesn't contain the newly added phase.
What is the strategy when Hudson needs to handle different version of maven with different
components.xml definitions?
Confirmed with build 1.218.