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

Why does Bamboo run Java Specs with its own POM?

I've created some Java specs and tried uploading them but it seems that Bamboo tries to merge the specs project POM with one of its own; "bamboo-specs-generator". This caused me issues when declaring versions as properties, as properties weren't being merged into the new pom, but generally I wonder why bamboo is generating its own pom when my project has a perfectly good one already!

1 answer

1 accepted

1 vote
Answer accepted

Hi Alan,

By default Bamboo Specs are executed with a default pom.xml film, i.e. it will not use pom.xml from your bamboo-specs project. (from: Bamboo Specs troubleshooting)

You can find the default pom file at BAMBOO_INSTALL/atlassian-bamboo/WEB-INF/classes/bamboo-specs-pom.xml


Right. What is the benefit of this method? It seems like an arbitrary limitation (it won't improve security, for example) and an extra source of issues.

Like # people like this
Deleted user Jul 27, 2018

@Gabriel Ribeiro Just curious, if Bamboo doesn't use the pom.xml file from the bamboo-specs folder then why is it even required in the first place?

Like # people like this

I'm also curious. Why does bamboo use a default pom even in a case where there is a pom? 

It would make sense to use a default pom when there's none available, otherwise use provided pom.

@Gabriel Ribeiro what is the reasoning around using a default pom always?

Hi @Ivhani and @[deleted] 

Since the specs build will run inside the same environment as Bamboo, The POM gets sanitized by default to avoid less experienced users (or bad intentioned ones) to import dependencies that can potentially damage Bamboo.

You can disable this behavior (at your own risk) by adding the following property to <installation directory>/bin/ and per Configuring your system properties documentations.

Like Ivhani likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events