Trying to configure various changeset conditions, cache-keys or clear-cache steps does not help the fact that you need to re-download the dependencies all the time after a cache is cleared/not found.
My suggestion is to add a configuration option that will allow to cache to be re-uploaded with the new contents.
definitions:
caches:
maven-cache:
replace: true
path: ~/.m2/repository
Then a project could add a new dependency and have it added to the cache without having to clear the old one.
