[news.eclipse.platform.pde] Re: "Unsatisfied version constraint" after a

[Richard Fearn <eclipse@xxxxxxxxxxxxxxxxxx>]

I've had this problem; my situation might not be exactly the same as yours, but this might give you some clues as to where to look...

We currently have a large 'libs' plugin that has many third-party JARs, and just exports every package from every JAR. Our other plugins have up to now depended on 'libs'.

We're now removing JARs from 'libs' and gradually replacing 'libs' with 'real' OSGi bundles.

I removed the Spring JAR from our 'libs' project, and added the corresponding OSGi bundles to the projects that used to get that JAR from the 'libs' project.

Spring depends on Commons Logging, and that was still an 'ordinary' JAR in 'libs' (i.e. not an OSGi bundle with a specific version number). I had to replace the Commons Logging JAR with a bundle to get rid of the errors.

So the errors are misleading for two reasons:

1. You get "Unsatisfied version constraint" errors for every dependency, although it's just one that has a problem.

2. It can actually find the bundle, it's just that it can't satisfy the dependencies for that bundle (e.g. in my case it could find org.springframework.beans, but couldn't work out if the right version of Commons Logging was available to allow org.springframework.beans to be used).

Rich