mvn clean slow on Windows - alternative implementation

[atlib77]

Hi,

I've noticed that running 'clean' goal is really slow on Windows, especially compared to a Linux. I do understand file operations are much quicker on linux for sure. But I'm I mean e.g. 10 seconds vs <1 second difference!

So I wondered if the 'target' folder could simply be renamed to e.g. target_timestamp and let the build continue (renaming the folder is superquick). Then the daemon could take care of actually deleting the renamed folder afterwards in some low-prio background process.

Obviously it could be done in maven directly, but since it doesn't have the concept of a daemon, it couldn't go as far/fast.

btw, thanks for a great program! It really makes using maven much more bearable :)

[ppalaga]

Interesting idea! But cleaning is not necessarily just deleting the whole target folder. The clean plugin allows for defining some exceptions for files/folders that should not be cleaned. Hence there is some logic implementing that and I guess it would be hardly maintainable outside the clean plugin. Having said that I'd see this as a feature for the clean plugin.

[gnodet]

It should be possible to implement a custom extension / lifecycle to provide a fast clean phase implementation moving the folder and deleting it in the background (or not).

[gnodet]

@atlib77 an experimental extension is available in this PR #538

[atlib77]

Awesome! Left a comment on the PR #538

[gnodet]

Closing this issue as it has been moved to the clean plugin. https://issues.apache.org/jira/browse/MCLEAN-95