[
https://issues.apache.org/jira/browse/MINVOKER-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958394#comment-17958394
]
Olivier Lamy commented on MINVOKER-101:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-invoker-plugin#436|https://github.com/apache/maven-invoker-plugin/issues/436].
> provide property to make a clean clone
> --------------------------------------
>
> Key: MINVOKER-101
> URL: https://issues.apache.org/jira/browse/MINVOKER-101
> Project: Maven Invoker Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Affects Versions: 1.5
> Reporter: Robert Scholte
> Assignee: Benjamin Bentmann
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
