Problem Definition
Some customers will isolate the Maven repository at a more granular level to prevent downstream plans picking up libraries installed by an earlier failed builds. (The m2 repository is set at the agent level, instead of the plan level.) Adding a -Dmaven.repo.local argument is possible but it has to be done for every task individually.

Suggested Improvement

An good improvement for Bamboo would be a option for per-job or per-plan, which can be overridden in the Maven task would be preferred.

Workaround
One suggestion would be calling Maven via a wrapper and adding it there.