jira-importer commented on issue #135: URL: https://github.com/apache/maven-clean-plugin/issues/135#issuecomment-2690259372
**[Ryan Thoma](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ryan-sd)** commented What is the hold up on getting this bug resolved, since Andreas Kutschera offered a patch to address this 2 years ago? In the mean time, I will offer some additional thoughts: I like the earlier comment suggesting the "nice" thread and the "asynchClean" plugin option, but that is not enough. When thinking about build machines running continuously, there might be additional build steps after the "maven" step ends and I would really not want the "nice" async clean thread slowing them down. In a large multi-module build, this could also generate a ton of "nice" threads that would bog things down. We should have another way to do the move/rename approach but not the async clean, maybe something like "onlyRename"? In that case, it would be up to the user to make sure they occasionally run a full/default clean before their storage runs out of space. I would suggest tying together both scenarios above into a single plugin option: "cleanMode" which could be set to "asyncClean", "onlyRename", or "default" (i.e. normal delete clean behavior). I also like the old target getting renamed and put under the target directory like "target/oldTarget-DATE-TIMESTAMP". Including the DATE TIMESTAMP as part of the renamed directory would make it unique and help avoid a collision if this module was re-built/re-cleaned before the "nice" clean thread got a chance to run or if you were in the "onlyRename" mode. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
