Community
Answers Developer Questions
Questions
How do I manage different versions of the same dependency for different releases of Bamboo?

How do I manage different versions of the same dependency for different releases of Bamboo?

With the release of 4.2, I found my plugin incompatible with Bamboo. I rely on the 1.8.18 version of the bamboo git plugin.

&lt;dependency&gt;
			&lt;groupId&gt;com.atlassian.bamboo.plugins&lt;/groupId&gt;
			&lt;artifactId&gt;atlassian-bamboo-plugin-git&lt;/artifactId&gt;
			&lt;version&gt;1.8.18&lt;/version&gt;
			&lt;scope&gt;provided&lt;/scope&gt;
		&lt;/dependency&gt;

However, 4.2, is bundled with 1.9.9. Is there a way to tell my plugin to use the default git plugin bundled with the current Bamboo release? I'm not sure how to define this in OSGI. If I bump up the version, then my plugin isn't going to maintain compatibility with previous releases correct? Any input is greatly appreciated.

Update:

I tried switching to 1.9.9 and my plugin still will not load:

&lt;dependency&gt;
			&lt;groupId&gt;com.atlassian.bamboo.plugins&lt;/groupId&gt;
			&lt;artifactId&gt;atlassian-bamboo-plugin-git&lt;/artifactId&gt;
			&lt;version&gt;1.9.9&lt;/version&gt;
			&lt;scope&gt;provided&lt;/scope&gt;
		&lt;/dependency&gt;

I get the following error:

2012-09-04 12:00:45,700 ERROR [pool-11-thread-1] [OsgiPlugin] Detected an error (BundleException) enabling the plugin 'com.houghtonassociates.bamboo.plugins.gReview' : Unresolved constraint in bundle com.houghtonassociates.bamboo.plugins.gReview [57]: Unable to resolve 57.0: missing requirement [57.0] package; (package=com.atlassian.bamboo.plugins.git). This error usually occurs when your plugin imports a package from another bundle with a specific version constraint and either the bundle providing that package doesn't meet those version constraints, or there is no bundle available that provides the specified package. For more details on how to fix this, see http://confluence.atlassian.com/x/1xy6D

2012-09-04 12:00:45,707 WARN [pool-11-thread-1] [OsgiPlugin] Unable to enable plugin 'com.houghtonassociates.bamboo.plugins.gReview'

com.atlassian.plugin.osgi.container.OsgiContainerException: Cannot start plugin: com.houghtonassociates.bamboo.plugins.gReview

I checked the plugins directory and see the jar for the referenced plugin:

bamboo\home\bundled-plugins\atlassian-bamboo-plugin-git-1.9.9.jar

How am I supposed to load this plugin and still maintain backwards compatibility?

Why is there a reference to a tiny URL which doesn't exist? http://confluence.atlassian.com/x/1xy6D

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote

Answer accepted

Hi Jason,

At compile time, your classpath dependencies are controlled by maven. At runtime, your classpath dependencies are controlled by OSGi. There is quite a lot of documentation floating around on OSGI, Spring, Atlassian plugins, and how they all fit together. For example, you may like to browse through:

When your plugin is installed, the Atlassian plugin framework does some byte-code scanning and other trickery to look at your plugin and try to build an appropriate OSGI bundle and corresponding manifest. This manifest is what explicitily lists the dependencies that your plugin requires at runtime. The auto-generated manifest is not very intelligent and can, in circumstances like this, fail to generate what you require.

The solution is to take over from the automatic process and provide instructions in the atlassian-plugin.xml on what you want to be specified in the manifest. For information on how to do this, have a look at the documentation on:

You need to add an Import-Package element to your bundle instructions that specifies a version range to your dependency on the bamboo-git-plugin. For example:

&lt;atlassian-plugin name="My Plugin" key="com.example.plugin" plugins-version="2"&gt;
    &lt;plugin-info&gt;
        &lt;version&gt;${project.version}&lt;/version&gt;
        &lt;bundle-instructions&gt;
            &lt;Import-Package&gt;
              com.atlassian.bamboo.plugins.git;version="[1.8.18,1.9.9]"
            &lt;/Import-Package&gt;
        &lt;/bundle-instructions&gt;
    &lt;/plugin-info&gt;
&lt;/atlassian-plugin&gt;

This instruction tells OSGi and the plugins framework that your plugin requires classes from the com.atlassian.bamboo.plugins.git package, but that the dependency can be satisfied with either version 1.8.18 or 1.9.9 of that package (and anything in between). The automatically generated manifest does not include this version range, and explicitly adds the version that was found in your pom.xml.

Also note that once you specify bundle-instructions in your plugin XML, you now have to list all the dependencies you want to import - including those from bamboo core. This completely overrides the automatic manifest generation.