gnodet commented on issue #8518: URL: https://github.com/apache/maven/issues/8518#issuecomment-4110310496
This issue is fixed in Maven 4 through a fundamental architectural change in dependency injection. Maven 4 replaced the Guice-based DI system with its own native DI implementation: - Commit `1f97959a11` — Set Guice class loading to CHILD - Commit `780a5cb67c` — Ban "plain" Guice usage - [MNG-7947] and [MNG-8525] — New Maven DI system Maven 4's DI system does not rely on JSR 330 annotations being discovered via Guice's custom binding mechanism. Instead, Maven 4 uses its own component discovery and injection system that properly handles all binding scenarios, including those from extensions and plugins. The original issue (Guice not picking up custom `Module` implementations for `@Named` bindings) is no longer applicable because the Guice-based binding infrastructure has been replaced entirely. _Claude Code on behalf of Guillaume Nodet_ -- 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]
