cstamas commented on issue #315: URL: https://github.com/apache/maven-clean-plugin/issues/315#issuecomment-4844354326
This is totally out of the scope for this plugin. From site: https://maven.apache.org/plugins/maven-clean-plugin/ > The Clean Plugin is used when you want to remove files generated at build-time in a project's directory. Your ask is to go beyond project's directory. I would argue this is developer (yours) or possibly SCM tool (ie git) job to do. What you effectively want, is m-clean-p to perform `git clean` for you, which is IMHO a nonsense. Did you leave them there BEFORE doing the checkout update? Yes Did you perform `mvn clean` BEFORE updating the checkout? NO Is the clean plugin failing to remove them? Usually when a module is refactored (removed, renamed or removed), hence, that directory goes "out of the scope" for project. And, by definition above, clean nor maven itself will not try to figure out what should it do with it (should it look into SCM history and figure out "this was a module, but removed/moved"? Or should go berserk and no not-a-Maven directory should exist within project, should Maven just remove `/docs` and everything blindly?) -- 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]
