[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.technology.buckminster] Re: Problems with Buckminster not correctly resolving all dependencies

Hi Adrian,

Adrian Skehill wrote:
Now when I run Buckminster to resolve all our components, it fails to pull in a few of them that are identified as dependencies, e.g. org.apache.batik.bridge requires rg.apache.batik.css.engine but this plugin was not imported into the workspace and I get some failures.
>
I think I found this problem. The org.apache.batik.bridge bundle doesn't require any other bundles. It does have a quite a few package imports though, but a package import doesn't say anything about what bundle it is that provides that package. Buckminster has no way of guessing this.


What you need to do in order to resolve this is to create a feature or a top-level cspec somewhere that includes all bundles needed in order to satisfy the package imports.

Hope this helps,

Regards,
Thomas Hallgren