This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

Dependency resolution in bundle project

Mar 24th, 2009, 03:30 PM

Hi,

I'm just starting to use Spring IDE 2.2.2 and I have some trouble for resolving bundle dependencies.
I've have a bundle (let's call it A) configured with Spring dm as the target runtime. bundle A dependencies with bundles in spring-dm are correctly handled, they appear in the bundle dependencies folder when the Import-Package is added in manifest.mf.
Now bundle A has also imports some package from bundle B, another bundle of my eclipse workspace. The imported package is correctly exported from bundle B and imported in bundle A. But the dependency is not resolved (bundle B doesn't appear in bundle A dependencies), just like if workspace resolution was not working.

Comment

This doesn't change the problem.
template.mf only allows MANIFEST.MF auto update.
My problem is that when editing the MANIFEST.MF file, in the runtime folder I can add some import which is displayed it the list. But once it is added, it generates the error shown in my first post.
I guesst this will work at runtime, but in eclipse IDE this generates an error in MANIFEST.MF and also prevents source code from being compiled (error in package import in java classes).

The only way for now to make it work is to add the project which exports the package as a referenced project into the project which imports it.