[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] issue with optional imports

I've encountered the very same thing usingÂ3.10.100.v20140909-1314 (built from source)

This happens even if the same bundle providing the optional package is reinstalled.

Thus, if the bundle is there when first resolving the "client" bundle, everything is great. The moment either bundle is re-resolved, then the optional package does not wire.

- Ray

On Wed, Oct 15, 2014 at 8:49 AM, Martin Lippert <mlippert@xxxxxxxxx> wrote:

I have an issue with optionally imported packages and I have no idea what is exactly going on or how to diagnose this in more detail.
We have a bundle that defines Import-Package, marked as optional.


There is a bundle (org.eclipse.m2e.maven.runtime) that exports this package and everything is wired just fine.
Now I install a new version of m2e and therefore the exporting bundle is updated to a new version.

But after the update, the optional package import is not wired again. I would expect this to be wired to the new version of that org.eclipse.m2e.maven.runtime bundle, but that doesnât happen. There are no other bundles in the system that export this package. A âdiag <bundleID>â (with the bundle ID of the importing bundle) doesnât return anything.

Any idea what might be going on? All this is on Equinox 3.10.1.v20140909-1633 (Luna SR1, I think).
Or any idea how to investigate this in more detail?

(I already tried to restart Eclipse with -clean, but the result is the same, the optional import isnât wired and I donât see a potentially package-use conflict anywhere)

Thanks a lot for your help!

equinox-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Raymond AugÃÂ(@rotty3000)
Senior Software Architect
Liferay, Inc.Â(@Liferay)