desruisseaux commented on issue #109: URL: https://github.com/apache/maven-clean-plugin/issues/109#issuecomment-2825210101
We can see the 3.4.1 behaviour as a regression, or the 3.4.0 behaviour as a bug. Both views are defensible. A compromise could be to default to `true` for now with a warning saying that the default would change to `false` in a future version (that warning would not be emitted if the user explicitly set that option). A reason for safety is that there is always a risk that the directory to delete is accidentally set to the wrong directory. Or maybe there is a symbolic link pointing outside the target directory (e.g. users created it temporarily for a test, then forgot about it) and the plugin is following symbolic links. If a file is marked as read-only, it is probably of particular importance for the user, so being conservative is a common choice. -- 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-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
