Third party jars with conflicting dependencies

[Spencer Michaels]

I'm writing a Bamboo plugin that relies on a 3rd-party jar. This jar itself uses a version of the Spring framework, which causes a conflict with the version that Bamboo uses. I need to figure out how to resolve this dependency conflict.

I have installed my jar into my local maven repo and added it as a compile-scope dependency:

 <dependency>
   <groupId>com.my.jar</groupId>
   <artifactId>jarId</artifactId>
   <version>1.0-SNAPSHOT</version>
   <scope>compile</scope>
   <exclusions>
     <exclusion>
       <groupId>org.springframework</groupId>
       <artifactId>*</artifactId>
     </exclusion>
   </exclusions>
 </dependency>

I have also added a plugin dependency in the maven-bamboo-plugin configuration.

<pluginDependencies>
  <pluginDependency>
    <groupId>com.my.jar</groupId>
    <artifactId>jarId</artifactId>
  </pluginDependency>
</pluginDependencies>

The result is that my plugin fails to load because of several springframework-related class conflicts, so it looks like the jar is getting bundled with the plugin, but the excludes are getting ignored. What do I need to do to resolve this?