The JcrDriverIntegrationTest has been failing for some time on the Hudson boxes, yet it's been running successfully on developer boxes. Turns out the problem is in a base class (ModeShapeUnitTest extended by ModeShapeMultiUseTest extended by JcrDriverIntegrationTest) and how the 'startEngineUsing(...)' method works when supplied with the path to the configuration file that should be on the classpath. When this method is called in a static method (e.g., the @BeforeClass method), the classloader is null and the method looks for the configuration file on the file system and then under 'src/test/resources'. That's obviously a problem when the configuration file has Maven replacement properties, and the real file is placed by Maven under 'target'.

The 'startEngineUsing' method needs to take the class under test as an additional parameter, and the JcrDriverIntegrationTest needs to use this new method.