I've tried hard coding the resource bundle path and I get the same result. And it only happens about half the time, regardless.
Judging by the stack trace, the problem is somehow related to what happens when Surefire forks so that the tests run in their own JVM process. When I set "forkMode" to "never", I don't get the error any more but several of my tests fail because they require their own process. Let me know if anyone has any other ideas. -- View this message in context: http://maven.40175.n5.nabble.com/Surefire-NPE-tp3246444p3258956.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
