gnodet opened a new pull request, #12556: URL: https://github.com/apache/maven/pull/12556
## Summary Backport of #12554 to `maven-4.0.x`. - Bumps Eclipse Sisu from 1.0.1 to 1.1.0 - Fixes extension realm visibility so that Sisu 1.1.0's new JSR330 bean filtering works correctly with Maven's ClassRealm hierarchy ## Root Cause Sisu 1.1.0 introduces `jsr330ComponentVisibilityFollowsPlexusVisibility` (on by default), which filters beans based on ClassRealm visibility via `RealmManager.computeVisibleNames()`. This BFS traversal walks parent and import realms from the current TCCL. Extension realms have `plexus.core` as their parent, but beans discovered in the container are sourced from the `maven.ext` realm. Since extension realms had no import relationship to `maven.ext`, container-sourced beans were incorrectly filtered out when TCCL was set to an extension realm during lifecycle callbacks (e.g., Mimir extension). ## Fix Adds a reverse import from each extension realm to the container realm (`maven.ext`), using the same `importFrom(realm, realm.getId())` pattern already used for the forward direction. This works **with** Sisu 1.1.0's filtering feature — the realm visibility graph is corrected to reflect the actual relationship between extension and container realms. ## Verified - ✅ Clean cherry-pick from master (no conflicts) - ✅ `mvn clean install -DskipTests` passes on 4.0.x - ✅ `mvn verify -pl impl/maven-cli` passes (581 tests, 0 failures) - ✅ Build succeeds with Mimir extension enabled - [ ] CI build passes 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
