gnodet opened a new pull request, #13676: URL: https://github.com/apache/maven/pull/13676
Backport of #13650 to `maven-3.9.x`. `MavenCli#initialize` resolved `multiModuleProjectDirectory` with `File#getCanonicalFile()`, which asks the OS to resolve the path and can follow a symlink, a junction, or (on Windows, since JDK-8355342) a mapped network drive to a different location. That corrupts the reactor root, so every module/parent path resolved against it afterwards breaks (the `H:\\colo-01-fs02\\...` path in issue #11167, reported against 3.9.11). Routed through the same `getCanonicalPath(Path)` helper this class already uses elsewhere since #11250, which only normalizes lexically (`toAbsolutePath().normalize()`). **Note:** on `maven-3.9.x` the `getCanonicalPath()` helper itself still used `toRealPath()` — fix #11250 was never backported here. This PR also fixes that helper to use `toAbsolutePath().normalize()` consistently. **Conflict resolution:** cherry-picked manually due to the `compat/`/`impl/` → bare module path divergence. Applied to `maven-embedder/` (no prefix on 3.9.x). -- 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]
