desruisseaux commented on issue #109: URL: https://github.com/apache/maven-clean-plugin/issues/109#issuecomment-3534203662
Hello @cowwoc. My understanding of [previous comment](https://github.com/apache/maven-clean-plugin/issues/109#issuecomment-3164564686) is that some peoples perform a `git` checkout in the target directory. Git creates a hidden `.git` directory with read-only files in it. I think that git wants those files to be read-only because they may be shared (with hard links) with other git checkouts. On Unix systems, this is not a problem because the read-only flag blocks only modifications of the file, not deletions. But Windows is different: on that OS, the read-only attribute blocks both modifications and deletions. So, in my understanding of this discussion, the use case is a Windows-specific problem of users who perform `git` checkout in their target directory. This is understandable for [testing Maven SCM](https://github.com/apache/maven-clean-plugin/issues/109#issuecomment-3164564686) for example, but I would find strange and inefficient if it was done in other contexts. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
