Details
-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
None
-
None
Description
Currently the JUnitBundleTestRunner uses code like this
public TestResult execute(Class<?> testClass, String methodName) { ClassLoader ctxLoader = Thread.currentThread().getContextClassLoader(); try { // Make sure we run in the context of the arquillian-bundle class loader Thread.currentThread().setContextClassLoader(getClass().getClassLoader()); return super.execute(testClass, methodName); } finally { Thread.currentThread().setContextClassLoader(ctxLoader); } }
This causes issues with APIs that use the TCCL for resource discovery. Investigate why the TCCL is used at all and whether the testClass CL could be used instead
Attachments
Issue Links
- is blocked by
-
ARQ-1880 Arquillian core relies on TCCL to load infra
- Closed