[
https://issues.apache.org/jira/browse/MCLEAN-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223695#comment-16223695
]
Matthew Ouyang commented on MCLEAN-79:
--------------------------------------
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.
> Partial Clean + Configurable Selectors
> --------------------------------------
>
> Key: MCLEAN-79
> URL: https://issues.apache.org/jira/browse/MCLEAN-79
> Project: Maven Clean Plugin
> Issue Type: New Feature
> Affects Versions: 3.0.0
> Reporter: Matthew Ouyang
> Labels: features
> Attachments: clean-partial.patch
>
>
> Partial cleanup would be useful in situations where source files are deleted
> or changing between feature branches (which also can result in deleted source
> files). This would eliminate the need to do a full clean.
> Looking for feedback on provided patch. To enable this, Selectors need to be
> configurable + some POC implementations (IdentitySelector, JavaSelector) have
> between provided. The patch also includes a page that describes the new
> feature in more detail, and Selectors have been placed in a separate package
> (now that there is more than one implementation).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
