cstamas opened a new issue, #13583: URL: https://github.com/apache/maven/issues/13583
### Affected version 3.10.0 ### Bug description There is a bug in 3.10.0 that causes that (all bullets are logically AND): * there is one or more core extension present in system * any of core extension tries lazily (so not on load, but programmatically) create components * filtering will prevent provisioning them, causing error Reason is JSR330 bean filtering. Typically, when lifecycle participant is invoked from `DefaultMaven`, the TCCL is set to that extension ClassRealm. But, Maven, when core extension _is present in system_ created a slightly different classloader hierarchy: it will create new realm `maven.ext` that uses `plexus.core` as parent, and imports each core extension realm exported items, and finally will use `maven.ext` as "container realm" to create Plexus DI. This implies, that (now with visibility), no core extension, with TCCL set to that core extension realm, can "see" any core component. This applies only to "lazily created" components. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
