-
Enhancement
-
Resolution: Done
-
Major
-
None
ChildFirstClassLoader and LegacyKernelServicesInitializer have hooks to allow tests to prevent classes from being loaded from the parent CL, but there's no way to prevent resources being loaded. In particular META-INF/services files, which bit us with https://github.com/wildfly/wildfly-core/pull/3685 as a META-INF/services file in the parent was being found when trying to load services for an interface in the child CL. The impls in the parent could not implement the child CL version of the interface. Excluding loading of the META-INF/services file in the paren solved the problem.
- clones
-
WFCORE-4405 Binary jar files in model-test
- Resolved
-
WFCORE-4346 ChildFirstClassLoader and LegacyKernelServicesInitializer should allow exclusion of resources from the paren
- Resolved
- is incorporated by
-
JBEAP-16580 (7.2.z) Upgrade WildFly Core from 6.0.12 to 6.0.14
- Closed