Applying the patch mentioned has made running annotation based testng tests b0rken. Ie before it was loading classes using a context of system class loader. I've fixed this locally by calling createClassLoader(classpathurls, childdelegation, true) (which uses system class loader by default) instead of createClassLoader(classpathurls, null, childdelegation, true).
The recent application of old patches is definitely appreciated, but things like this make me nervous for the future. There ~has~ to be a reasonable way to run unit tests against surefire that assert things aren't broken...The logic of classloader dependencies is too fragile to not have tests... Sorry, I shouldn't be telling you guys what to do.. -- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
