Add 'force' option to maven clean plugin
envgap__oshi__oshi-2899
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- The project already builds and runs before the fix, so there is nothing to repair.
02 / ENVIRONMENT RECIPE
- Base commit
a24ac6b821a45de8852f9d1c49c129ce28fe8780- Manifest
pom.xml- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
oshi/oshi #2899 · read the original issue
@dbwiddis Maven really messed up the clean plugin, you may have likely ran into 'checkout' file in target folder getting stuck and needing deleted manually. Instead of fixing that defect from 3.4.1 correctly, they added a new flag you have to set manually. I'm busy with a lot of other issues related to this so I don't have time to do here but wanted to open a ticket and mention to just add ```<force>true</force>``` to the clean plugin configuration so that it returns to behavior of cleaning up all of the temp 'target' folders.
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]