Hi
Am 09.02.2026 um 12:25 schrieb Stefan Bodewig:
Many thanks Jens, this is exactly why I asked people to test the release
candidate.
Can you tell us which version of Java you are using?
I suspect you are using Java < 24 and things would break with Java 24+
(i.e. the current LTS of 25) for you even when using Ant 1.10.15.
Prior to Java 24 File#getCanonicalPath does not follow junctions or
symlinks on Windows while Path#toRealPath does. One change in 1.10.16 is
to use Path#toRealPath here. But if I'm correct, then the change to
getCanonicalPath in Java 24+ would have the same effect on your build.
Yes, you are right. I first run it with JDK17 and testet it now with
JDK21 and JDK25 with your expected result.
For your specific case we probably need something like followSymlinks on
<property> that you would need to set to false in order to resolve the
file the same way as before.
This would be a valid workaround I think.
Jens
On 2026-02-09, Jens Hofschröer wrote:
I think this _will_ break some builds. At least mine.
I am working inside a folder from a junctioned path. In my buildscript
I need to find a relative path to a file. This works find in 1.10.15.
With the release candicate 1 this no longer works an my build breaks.
I created a simple sample script to demonstrate the difference:
[cut]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
