jira-importer commented on issue #132: URL: https://github.com/apache/maven-clean-plugin/issues/132#issuecomment-2690258800
**[Nick Pellow](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=npellow)** commented My plugin consists of several MOJOs. One of which runs at the end of the build, storing some state about what happened during the build. This data is optionally required for following builds, allowing the build time to be drastically reduced. > For instance, what generated the files to exclude, your plugin or something else? Yes, the same plugin generated the files to exclude. However, conceivably they could be produced by any plugin. > If the files should be excluded from cleaning, why aren't they put somewhere else? They can optionally be put somewhere else. This requires extra configuration (and effort) by the user however. The target directory is the best location for these files however, since they will be removed when the user runs the clean goal, without running my plugin first. > How can they ever be deleted by Maven or isn't that intended? By simply running $> mvn clean, without my mojo being explicitly called first. Also, my mojo will be able to decide when those files are to be deleted. Apart from the use case I describe above, I see this patch to be providing the extremely useful ability to specify excludes and includes on the command line. -- 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
