Automatic Dependency Management in Bamboo 3.x with Maven 2 fails

I have a multi-project build structured thusly:

|-> parent2
      |-> parent 3
            |-> project1
            |-> project2
            |-> etc

I see the following error in Bamboo when building with Maven 2 in several of my projects (all of them under parent3):

Automatic Maven plan dependencies processing failed: Cannot find parent: parent1.parent2:parent2 for project: parent1.parent2.parent3:parent3:pom:null for project parent1.parent2.parent3:parent3:pom:null

Notice the version coordinate is "null". We only declare a version in the top-level parent1 pom. parent2 and parent3 don't specify any version info, they simply inherit it from parent1. Given that parent3 is one step removed from that inheritance, maybe that's why the version string is "null" in the coordinates rather than properly found? The automatic dependency detection works for direct dependents of project2, and it doesn't have a version element in the pom either.

This has happened since Bamboo 3.0, but at least the builds completed. It still happens in 3.1 but the 'Automatic Maven dependencies' task now treats that as a build failure, so now my builds are "failing" even though the maven build task was successful. Moving from the Maven 2 builder to the Maven 3 builder works, but we have some projects where we're not ready to move to Maven 3 yet. Another interesting fact: only projects under parent3 see this problem - projects that are direct children of parent2 and parent1 work just fine. Anybody else have this problem or something similar?

3 answers

A quick test of adding version declarations to each of the parent poms still exhibits the error. It's almost as if the automatic dependency plugin can't walk up more than one step.

Another strangeness... why does changing the Maven build task from Maven 2 to Maven 3 affect the Automatic Maven dependencies task? Aren't they isolated excutions? I'm assuming the autmatic dependencies task is using the Maven embedder and resolving the dependencies on it's own, but the "fix" for this problem on 3.1 (at least for me) is to delete the Maven 2.x builder task and use a Maven 3.x builder task.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Feedback & Announcements

How do you analyze GC logs, thread dumps and head dumps?

Hi awesome community!  In this article, I would like to describe the one of the toolset (service) for the analyze some problems on different Java-based instances, of course, as Atlassian admini...

94 views 0 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you