On Fri, 28 Nov 2025 18:29:42 GMT, Francisco Ferrari Bihurriet <[email protected]> wrote:
>>> Hi folks, as we know [JDK 26 enters Rampdown Phase One next >>> week](https://mail.openjdk.org/pipermail/jdk-dev/2025-November/010639.html) >>> on Thursday, 4 December. >>> >>> Please let me know if we'll want this fix to move forward before that >>> happens, and please note that soon I will need to focus on the OJVG work. >>> >>> If you prefer, I'm fine with using `path.toRealPath()` instead of >>> `path.toFile().getCanonicalFile().toPath()`. That would keep relative >>> includes broken in _Windows_ UWP Java applications and from _Linux_ >>> anonymous pipes and files (where they don't make a lot of sense anyway). >>> But that is better than the current status quo (_Windows_ UWP Java >>> applications break if they load the `java.security.Security` class). >>> >>> Just let me know if you want to proceed that way and I will, also removing >>> the part of the new test that will break by that change. >> >> Yes, I agree that seems like a way forward, if not perfect. @AlanBateman ok >> with you? > > @seanjmullan: with the hope of moving this forward before the JDK 26 > Rampdown, I went ahead and implemented the remaining two suggestions. I have > re-run the listed test categories from the description in _Windows_ and > _Linux_, everything is passing. It should be ready for a final review now. @franferrax I think it would be useful to update the PR description now that the fix is different than what was originally proposed. ------------- PR Comment: https://git.openjdk.org/jdk/pull/24465#issuecomment-3602101766
