Add option: `maven.build.cache.forceRenew`

[zorglube]

Following this checklist to help us incorporate your contribution quickly and easily:

• [ ] Make sure there is a MBUILDCACHE JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes.
• [ ] Each commit in the pull request should have a meaningful subject line and body.
• [ ] Format the pull request title like [MBUILDCACHE-XXX] - Fixes bug in ApproximateQuantiles, where you replace MBUILDCACHE-XXX with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message.
• [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• [ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
• [ ] You have run the Core IT successfully.

If your pull request is about ~20 lines of code you don't need to sign an Individual Contributor License Agreement if you are unsure please ask on the developers list.

To make clear that you license your contribution under the Apache License Version 2.0, January 2004 you have to acknowledge this by using the following check-box.

• [ ] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

• [ ] In any other case, please file an Apache Individual Contributor License Agreement.

[AlexanderAshitkin]

Hi @zorglube You are likely looking for the maven.build.cache.skipCache property. If the property is set to true, the build doesn't use any of the cached artifacts but writes the results to the cache (if allowed by config), effectively achieving the forceRenew functionality.

[zorglube]

Damn I didn't understood that.

Do you have any examples of the configuration needed to achieve that?

Still my idea is more "renew all the cache" than "rebuild all the results without using the cache".

[AlexanderAshitkin]

Damn I didn't understood that.

Do you have any examples of the configuration needed to achieve that?

Still my idea is more "renew all the cache" than "rebuild all the results without using the cache".

If you use this option, it will be a "clean" build without using the cache, and everything will be re-uploaded to the server. Effectively, all the cache outputs will be replaced with fresh results - it is effectively a forceRenew option you're looking for. It has no config because it was considered an emergency option, not something permanently enabled. Usage is simple - -Dmaven.build.cache.skipCache=true on the command line.

[zorglube]

Damn I didn't understood that. Do you have any examples of the configuration needed to achieve that? Still my idea is more "renew all the cache" than "rebuild all the results without using the cache".

If you use this option, it will be a "clean" build without using the cache, and everything will be re-uploaded to the server. Effectively, all the cache outputs will be replaced with fresh results - it is effectively a forceRenew option you're looking for. It has no config because it was considered an emergency option, not something permanently enabled. Usage is simple - -Dmaven.build.cache.skipCache=true on the command line.

Hello @AlexanderAshitkin,

I miss time nowadays, still I don't leave on the PR.