Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bamboo automatic dependency management with Maven

I set up two parent and child projects as described but Bamboo does not find parent dependencies in the child project and there is absolutely no other tutorial/documentation on this subject. Would you please provide a step-by-step example on how to set up automatic dependency management with Maven?

1 answer

0 votes

Hello @Mohammad Alavi welcome to the community :)

Are you facing issues with the child project not being able to fetch dependencies built by the parent project?

Also, the documentation that you have pointed out contains a section about automatic dependency management, what in that section didn't work for you?

According to the documents I expect the child build plan to be triggered when the parent builds successfully, but this does not happen.


This is my parent project POM file:

<project xmlns=""




and this is my child project POM file which depends on the parent project:

<project xmlns=""





Thanks for the pom.xml!

Can you also share the "Maven Dependency Processor" task configuration and the plan dependencies configuration you have on your both parent and child plans?

I used maven dependency processor task with default configurations (all fields are empty) both in parent and child projects in the default stage's default job.


Screen Shot 2019-11-26 at 19.54.57.png


and the plan's dependency configuration for both child and parent projects is as follows:


Screen Shot 2019-11-26 at 19.54.13.png

At first glance everything looks fine.

Giving a look at, branches are not capable of triggering dependencies. Did you tried to trigger your child plans from the parent master?

Yes I use master branch for both parent and child project 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events