Bamboo automatic dependency management with Maven
Asked by Mohammad Alavi:

I set up two parent and child projects as described <https://confluence.atlassian.com/bamboo/setting-up-plan-build-dependencies-289276887.html> 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?


Answers:
author: Victor Debone
body: Hello [@Mohammad Alavi](/t5/user/viewprofilepage/user-id/3618786) 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?

comments: author: Mohammad Alavi
body: 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="http://maven.apache.org/POM/4.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>me.smash.bamboo</groupId>
  <artifactId>parent-project</artifactId>
  <version>1.0</version>

...

</project>
```

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

```

<project xmlns="http://maven.apache.org/POM/4.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>me.smash.bamboo</groupId>
  <artifactId>child-project</artifactId>
  <version>1.0</version>


  <dependencies>
    <dependency>
      <groupId>me.smash.bamboo</groupId>
      <artifactId>parent-project</artifactId>
      <version>1.0</version>
    </dependency>
  </dependencies>

...

</project>
```


author: Victor Debone
body: 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?


author: Mohammad Alavi
body: 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](https://community.atlassian.com/t5/image/serverpage/image-id/74138iD6389818F196A4BF/image-dimensions/474x378?v=v2 "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](https://community.atlassian.com/t5/image/serverpage/image-id/74140i48A1F7DC4451822A/image-dimensions/554x319?v=v2 "Screen Shot 2019-11-26 at 19.54.13.png")


author: Victor Debone
body: At first glance everything looks fine.

Giving a look at <https://jira.atlassian.com/browse/BAM-18381>, branches are not capable of triggering dependencies. Did you tried to trigger your child plans from the parent master?


author: Mohammad Alavi
body: Yes I use master branch for both parent and child project