We've recently been getting a problem with the Maven Dependency Processor failing to find the the parent pom build project and then failing our build. The actual maven build builds ok.
I've got a maven module projects setup to build the modules independently and a parent project which just publishes a pom (with -N). We've been using automatic dependency management. I recently renamed the pom versions from a "1.0.0-SNAPSHOT" to just a "trunk-SNAPSHOT" convention. Ever since, the bamboo dependency processor errors out with this:
Automatic Maven plan dependencies processing failed: Cannot find parent: com.company.integration:integration-parent for project: null:application-manager-parent:pom:null for project null:application-manager-parent:pom:null
Any tips on how the processor actually links the maven poms to the bamboo builds?
Thanks for the question. Are you using Maven 3? My suspition is that you are stumbling on this bug, which is fixed in Bamboo 4.3. By the way, Bamboo 4.3 will be released next week.
If you are using Maven 2, and the dependency processor still fails for you, please open a ticket on https://support.atlassian.com and provide your build logs, Bamboo server logs and screenshots of your Bamboo task configurations.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot