Is there way to tell 3rd party jar to which version of dependency to use

[prathapvs]

Hi,

I am using apache servicemic 4.4.1 for deploying bundles. In my application i am using commons-codec(version 1.4) which has specific class implementation which is not there in earlier commons-codec(1.3). And also i am using acegi-security (version 1.7).

When i deploy the commons-codec and acegi-security jars in servicemix's deploy jar, acegi-security is using the default commons-codec(version 1.3) bundle which is already available in servicemix. So is there any way we can mention that the acegi-security to use the latest version.

When i tried to deploy my application bundle i am getting the below dependency error.

Error executing command: Unable to resolve module easymaker-runtime http://252.0 because it is exposed to package 'org.apache.commons.codec.binary' from org.apache.commons.codec http://245.0 and org.apache.servicemix.bundles.commons-codec http://56.0 via two dependency chains.

Chain 1:

easymaker-runtime http://252.0

import: (&(package=org.apache.commons.codec.binary)(version>=1.4.0))

export: package=org.apache.commons.codec.binary

org.apache.commons.codec http://245.0

Chain 2:

easymaker-runtime http://252.0

import: (package=org.acegisecurity.providers.ldap.populator)

export: package=org.acegisecurity.providers.ldap.populator; uses:=org.apache.commons.codec.binary

acegi-security http://251.0

import: (package=org.apache.commons.codec.binary)

export: package=org.apache.commons.codec.binary

org.apache.servicemix.bundles.commons-codec http://56.0

Edited by: prathap on Jul 19, 2012 5:26 AM

[ffang]

Hi,

The simplest way is you wrap acegi-security bundle yourself and add OSGi header like

Import-Package org.apache.commons.codec* with version range like [1.4, 1.5), so that your customer acegi-security bundle can resolve package from commons-codec 1.4.

Freeman

[prathapvs]

Hi Freeman,

        My app is dependent on several 3rd party jars (like around 30), and each might uses the other other jars like this. do we have to re build all the jars as bundle?

For ex. spring web jar uses -  commons-fileupload of older version and my app is using the latest version of fileupload.

Some 3rd party jars are already available in servicemix as bundles but version is different.

Is there any way to handle these problems?

--Prathap

[ffang]

Hi,

Yeah, per best OSGi practice, you should install all 3rd libs as bundles and servicemix already wrapped a lot of bundles(including different versions for same 3rd lib) for easy of use.

However, you can use a big umbrella jar and embed all necessary 3rd libs but you'll lose a lot of OSGi nature this way.

Freeman