[
http://jira.codehaus.org/browse/MCLEAN-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148238#action_148238
]
Nick Pellow commented on MCLEAN-38:
-----------------------------------
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.
bq. 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.
bq. 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.
bq. 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.
> Allow a global set of include and exclude filters
> -------------------------------------------------
>
> Key: MCLEAN-38
> URL: http://jira.codehaus.org/browse/MCLEAN-38
> Project: Maven 2.x Clean Plugin
> Issue Type: New Feature
> Affects Versions: 2.2
> Reporter: Nick Pellow
> Attachments: MCLEAN-38-maven-clean-plugin.patch
>
>
> I am about to submit a patch to the maven-clean-plugin which will allow a
> global includes and excludes patterns to be configured.
> Currently, it is not possibly to easily do a clean and have specific files in
> the default output directories preserved.
> The patch will allow a comma separated list of exclusions and inclusions to
> use when removing the default output directories.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
