On Thu, 13 Nov 2025 01:12:57 GMT, Francisco Ferrari Bihurriet <[email protected]> wrote:
>> Was just for a nicer error message, but I agree it could make things even >> harder to debug than an unresolved path. >> >> I will be changing this, adjusting the test case and re-testing. > > Done: 40bc832ef22670a6ba2481fb53d2ebe4b3bbd434 & > 4483469e453100259aa28d900943c34a4ab994b4. In line with this change and thinking about it again, I also removed path resolution from the debug messages: 7c80874c25bc99783ad24fb22d2c080d33c5503a. The test needed some adjustments but now the path resolution is only done when strictly necessary. This also prepares us in case we want to go back to `Path::toRealPath`, to only affect relative includes, but not logging messages. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/24465#discussion_r2564372917
