The automated Maven dependency management works great for detecting which plans are dependent on each other. This works very well.

However, this feature is next to useless when using multiple agents - especially the Elastic Bamboo agents. This is because when the triggered projects go to build, they can't find their dependencies.

As a manual work around, you can:

• publish the artefacts (build artifact and pom.xml) as Bamboo artefacts from the source project.
• download the artefacts in the destination project
• call 'mvn install:install-file' on the downloaded Maven artifacts so that they can be found during the build.

As a manual approach, this is very tedious, especially when setting up projects with several related dependencies.

All of this information is available to Bamboo, however, thanks to the Maven Dependencies Processor. That task needs a complement - a Maven Dependencies Artifact Downloader - which automates the steps described above.

(Note that this shouldn't require changes to the pom - unlike the deprecated Bamboo Artifact Sharing Maven Plugin)