[ http://jira.codehaus.org/browse/MSUREFIRE-66?page=comments#action_78022 ] Kenney Westerhof commented on MSUREFIRE-66: -------------------------------------------
I think this is fixed by my commit in revision 441092 (see SUREFIRE-54). The solution is to have 2 classloaders; one with the tests, and another one with surefire + testing framework, that has the tests-classloader as a parent. Close? > Fix classloader separation of Test NG > ------------------------------------- > > Key: MSUREFIRE-66 > URL: http://jira.codehaus.org/browse/MSUREFIRE-66 > Project: Maven 2.x Surefire Plugin > Issue Type: Sub-task > Components: TestNG support > Affects Versions: 2.2 > Reporter: Brett Porter > Fix For: 2.3 > > > Currently, all of the test classes go into the surefire classloader (as > before) so that TestNG can find them. > Using the context classloader might be the key to avoiding this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
