When we changed to use Maven 3 (see MODE-1096), we started explicitly specifying the versions for each of the Maven plugins, including the Surefire plugin that runs our unit tests. When we did this, we chose to use the latest version of Surefire (2.7.1), even though 2.7 had a severe change in behavior with respect to determining which unit test classes should be run. For details, see SUREFIRE-482, the release notes for Surefire 4.7, and the Surefire JUnit usage page.

Unfortunately, when I did the initial conversion to Maven 3, I didn't see the supposed warning message about running Maven with the "-Dsurefire.junit4.upgradecheck" argument, and therefore missed the fact that we were no longer running the TCK tests.