Re: [I] Clean fails in Windows Docker environment with 3.4.1+ [maven-clean-plugin]

["slachiewicz (via GitHub)" <gi...@apache.org>]

slachiewicz commented on issue #262:
URL: https://github.com/apache/maven-clean-plugin/issues/262#issuecomment-3378302012

   > After comparing Maven Clean Plugin versions 3.4.0 and 3.4.1, it is clear that the root cause of the reported issue is a major internal refactoring introduced in 3.4.1. In this release, the plugin migrated from using the legacy java.io.File API to the modern java.nio.file.Path and Files APIs for file and directory operations.
   > 
   > This migration brought changes such as:
   > 
   > - Replacing most usages of File with Path.
   > - Using Path.toRealPath() and other Files methods for directory and symlink handling.
   > - Changing the logic for directory traversal and deletion, now relying on DirectoryStream and Path-based operations.
   > As a result, the plugin now triggers code paths in the JDK (notably Path.toRealPath()) that are known to have issues with Windows reparse points and symlinks, especially in Docker environments where volume mounts are implemented as reparse points. This can lead to NoSuchFileException errors, as described in JDK bug JDK-8172711.


-- 
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: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org