jira-importer commented on issue #180: URL: https://github.com/apache/maven-clean-plugin/issues/180#issuecomment-2690264239
**[Peter De Maeyer](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=peterdm)** commented The stack trace is coming from `Cleaner.delete:300`, which is Maven code, not Java (JDK) code. There is no Java exception there. There are multiple complications there: on Windows or not, retries with `Thread.sleep`{^}(1)^ and back-off delays. This issue is missing a concrete situation illustrating an actual lack of information. Java's own `File.delete` API, which is used underneath, doesn't give more accurate information either besides `true` "delete successful" or `false` "delete unsuccessful". We could migrate to Java 7's improved `Files.delete` API, which instead throws exceptions with more accurate descriptions, but I would not do anything more beyond that. ^(1)^ `Thread.sleep` is almost always a bad idea. Could that maybe explain MCLEAN-102? In this case in particular, it looks like a random hack - what problem where they even trying to fix? But anyway, that is out of scope here. -- 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
