jira-importer commented on issue #190: URL: https://github.com/apache/maven-clean-plugin/issues/190#issuecomment-2690265041
**[Matthew Ouyang](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mouyang)** commented I didn't realize clean is a separate lifecycle altogether so thank you for pushing me to look into that altogether. I agree with you that we should be running `verify` instead of `clean install`. I understand your rationale for having individual plugins handle their own cleanup. I was worried about code duplication (particularly compiler and resources) and wanted to leverage the directory traversal code, but this seems like a minor worry because it is pretty easy to code a directory traversal. So what you are saying is that the compiler plugin would remove dangling class files, the resources plugin would remove dangling resources, and any plugin that takes part in the generate-sources phase will remove the sources it generates that later become orphaned. Finally, clean is the standby in case these plugins don't remove enough files. Correct? Please confirm and then I will implement. Lastly (this goes without saying) don't apply the patch. At least,, not yet. -- 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
