On Wed, 30 Apr 2025 17:36:52 GMT, Francisco Ferrari Bihurriet <fferr...@openjdk.org> wrote:
>>> File::getCanonicalPath seems to take the best-effort approach (both in >>> Linux and Windows), whereas Path::toRealPath is stricter. >> >> Path::toRealPath is doing the right thing, and consistent with realpath(2). >> The issue with File::getCanonicalXXX is that it is specified to return a >> canonical file even if it doesn't exist, so this is why you see a lot more >> code to compute a result. >> >> Maybe the recursive include check them maybe it should use the file key >> instead. > > @AlanBateman are you ok with letting the original > c6f1d5f374bfa9bde75765391d5dae0e8e28b4ab reviewers know of this fix and take > a look? Or do you think further discussion is needed somewhere else? @franferrax Is there any progress on this fix please? ------------- PR Comment: https://git.openjdk.org/jdk/pull/24465#issuecomment-2969670841
