Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Dependent jars for bamboo plugin not copied to remote agent

I am developing a plugin to manipulate resources in Azure.  This requires the use of several java libraries that implement the Azure API for Java.  These are defined as dependencies in my POM.xml file, and in my eclipse environment, they are visible to the compiler.

However, when running the plugin on a remote agent, the azure jar files are not available, though they have been before.

What would cause these jars to no longer be available on the remote agent?

1 answer

0 votes

Hi Jim,

What are you running on the remote agent, e.g. build plan or deployment project?

Also where are the jar files coming from, e.g. another build, are they artifacts, etc.?

In addition, can you please provide:

  • The steps to reproduce
  • If they are artifacts, please confirm they are shared



Thanks for the response, Brandon.

I am running a build plan on the remote agent, and the jar files I need are defined as dependencies in my pom.xml file for the plugin.  

The plugin is designed to allow the use of cloud resources (specifically Azure) in our Bamboo builds.  This requires the use of Java libraries that implement the Azure api, callable from java.  They are downloaded into my maven repository and unpacked in place if needed when I run Bamboo to work on the plugin.

I have discovered that when this happens, I can navigate to my      "<plugin>/target/dependency-maven-plugin-markers" directory and remove the markers, which causes the next build of my plugin to unpack the libraries again, and this has proven effective in working around this issue.

I am still curious as to why this may be happening periodically in my atlassian plugin development environment.  Unfortunately, I don't have any specific steps to reproduce the problem.



if you want to use some classes as part your plugin code they should included into your jar file and declared on MANIFEST.MF.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo Data Center - Early Access Program

G’day Bamboo customers, The wait is almost over! We are in the final stages of work on the first release of Bamboo Data Center, our self-managed enterprise offering of Bamboo. This Data Center offe...

953 views 0 16
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you