Resolver conflict that isn't a conflict

[Beta User]

Hi,

I'm getting the following error that just doesn't make sense. This is on a bundle that works perfectly well when run within Eclipse directly. I'm wondering if the supposed conflict is a false alert on the prefix...

Cannot resolve: MyBundle
Resolver report:
Bundle: MyBundle_1.0.0 - Uses Conflict: Import-Package: org.apache.commons.httpclient; version="3.1.0"
Possible Supplier: com.springsource.org.apache.commons.httpclient_3.1 .0 - Export-Package: org.apache.commons.httpclient; version="3.1.0"
Possible Conflicts: org.apache.commons.httpclient.protocol,org.apache. commons.httpclient.auth,org.apache.commons.logging ,org.apache.commons.httpclient.cookie,org.apache.c ommons.httpclient.params

[robh]

This is coming directly from the Equinox resolver and says that your bundle imports 'org.apache.commons.httpclient' which can be satisfied by 'com.springsource.org.apache.commons.httpclient_3. 1.0'.

The bundle 'com.springsource.org.apache.commons.httpclient_3. 1.0' and you bundle have crossing imports for 'org.apache.commons.httpclient.protocol,org.apache .commons.httpclient.auth,org.apache.commons.loggin g,org.apache.commons.httpclient.cookie,org.apache. commons.httpclient.params' and at least one of these is conflicting (probably based on version). My guess would be the org.apache.commons.logging import is conflicting.

Rob

[Beta User]

Yes. I missed that hiding in there. Mainly an issue as I'd thrown lots of jars together in one bundle where they weren't available as a bundle before.

Cheers,

Neale

[robh]

No worries - those uses clause violations are a bit of a pain to diagnose. I'm working on better automated diagnosis of those failures so this should get easier to spot in future releases.

Regards, Rob