slachiewicz commented on PR #159: URL: https://github.com/apache/maven/pull/159#issuecomment-5451099586
Closing this PR as stale — thanks @clarkperkins for picking up @ChristianSchulte's fork work and for the detailed PR description!\n\n**Rationale (based on codebase evolution since 2018):**\n\n- The patch modifies `DefaultModelResolver` and `ProjectModelResolver` in their **2018 file layout**; both classes have since been relocated and substantially reworked (Maven Resolver 1.x → 2.x, and the Maven 4 `impl/` core restructuring). The diff no longer applies conceptually, let alone literally.\n- The repository-merging semantics the PR tries to fix are now handled in a different part of the model-resolution pipeline.\n- The issue family remains tracked: [MNG-4347](https://issues.apache.org/jira/browse/MNG-4347) is still open (Reopened), and the closely related scenario "Super POM overwrites remapped central repository in nested dependencyManagement import POMs" is tracked separately in [MNG-6772](https://issues.apache.org/jira/browse/MNG-6772).\n\n**If this problem still reproduces on current Maven 3.9.x / 4.x** (import-scoped dependencies of direct dependencies not resolved using repo modifications from `settings.xml` profiles), please open a fresh PR against the current code with a reproducer test — ideally covering the MNG-6772 scenario too.\n\nThanks again for the contribution! -- 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]
