[
http://jira.codehaus.org/browse/MINVOKER-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MINVOKER-101.
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.6
Assignee: Benjamin Bentmann
Applied in
[r925763|http://svn.apache.org/viewvc?view=revision&revision=925763], thanks
Robert!
> provide property to make a clean clone
> --------------------------------------
>
> Key: MINVOKER-101
> URL: http://jira.codehaus.org/browse/MINVOKER-101
> Project: Maven 2.x Invoker Plugin
> Issue Type: Improvement
> Affects Versions: 1.5
> Reporter: Robert Scholte
> Assignee: Benjamin Bentmann
> Fix For: 1.6
>
> Attachments: cloneClean.patch
>
>
> I've got a usecase where a plugin generates files which are NOT written to
> the target-directory.
> This means these files won't be removed with a standard clean-goal configured
> inside the invoker-plugin, so it might (or should) result in failing tests.
> Think of the release.properties, only one difference: the release-plugin has
> it's own clean-goal. But in my case a separate clean-goal is just a bit of
> overkill. It would be nicer if this could be resolved with the invoker plugin
> itself.
> A patch is attached with the property cloneClean (default false to keep
> current and optimal behaviour) which will clean the directory if it's already
> there + an IT.
--
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
